|
|
|
|
| Index | Recent Threads | Unanswered Threads | Who's Online | Help |
DataNucleus Forum
DataNucleus Support
Environment : J2EE
Thread: Advice on Choosing a Java Web Framework
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
KarlMD
Novice Joined: Oct 10, 2005 Post Count: 20 Status: Offline |
Hello all, I am new to web programming in Java and find myself a bit overwhelmed by all of the options available for a web framework. I've done a bunch of web programming in ASP.NET (C#) prior to this as well as Java rich-client/GUI programming-- my current job. I like ASP.NET but after spending the last six months with JPOX and Eclipse, I find myself loathe to switch back to ADO.NET and Visual Studio 2005. All that aside: what web frameworks would you recommend I try out? From what I've read, I'm leaning towards Spring MVC or Tapestry but this is only based on a couple hours' worth of Googling. The things important to me are:
I'd really appreciate any input you can offer. It's hard to get a feel for what good coders actually like just by Googling for "java web framework". Thanks, Karl |
||
|
|
KarlMD
Novice Joined: Oct 10, 2005 Post Count: 20 Status: Offline |
Hello again, Well, after some more reading I've learned the distinction between Model 2 frameworks (e.g. Struts) and component-based frameworks (e.g. Tapestry and Wicket). Given my background in ASP.NET, I find myself a lot more comfortable with the component-based approach. Since it's newer and I like playing with shiny things, I'll probably look at Wicket first. Then I suppose I'll take a look at Tapestry, though I don't like what I've heard about its URLs. Does anyone have any experience with either of these two frameworks? Or does someone else here think using them is a bad idea for some reason? This is still more or less Day 1 for me in investigating web programming in Java, so I'm still very open to any input... Still searching, Karl |
||
|
|
rakesh
Novice Joined: May 9, 2006 Post Count: 24 Status: Offline |
Personally I try to stay with Echo2 and EchopointNG. It will not work in every environment, and is not very IE friendly (it is too outdated and buggy a browser a la Netscape 4). The main reason is I wish to stay totally in the Java domain, and do not particularly enjoy mucking around with HTML. |
||
|
|
apro1968
Newbie Russia Joined: Jun 20, 2010 Post Count: 1 Status: Offline |
Hi! Choosing a framework is a very difficult topic. No wonder so many people have already viewed your message, but only two tried to answer. 8-) Most of those who use some framework are unhappy with it. If someone is happy of a framework be sure he is a developer, not user. Let me try to make some comments on your message. Separation of HTML and Java code-- similar to ASP.NET's code behind scheme All we like to talk about separation of Java and HTML code. The problem here is that if we want to have varying HTML generated on the server side HTML by itself is not sufficient. Because it does not provide for conditional or iterative generation. So it would be more correct to speak about some minimal necessary adding of few constructs typical for programming language to HTML. These construct should be also this way or that way open to programming language context to choose branch or loop. So we may not expect a complete separation of HTML and programming language. Adding tags like <if> only camouflages the picture. However, besides what was said above, it is a very right thing to keep HTML ans Java code as separated as possible. (Which BTW is true about separating any code into smaller pieces). IHMO whatever the framework is it is all in your hands to keep those separate (unless your employer does permit only JSP files). Code behind scheme is IHMO just one of many possible solutions. The ability to use JPOX. I love it and never want to have to go back to rolling my own ORMs. Why should ORMs be at all a part of Web Framework? What is there specific to web in ORMs? I hate the so called Full Stack concept. It forces you to stick to a 800 pages of what you would probably choose to avoid, using your previous experience with other non-web frameworks. I believe that web Frameworks should limit themselves to web-related issue, keeping themselves open to coupling with ANY existing Java middle, side and back ware. The ability to do some form of site templating so that all pages have the same headers, footers, etc. Other words used used for this feature are "Code reuse". There may be in-application, in-company and wider code reuse. And that is about libraries of what is called user-tags or widgets. Most of implementations of code reuse are pretty messy. However have a look at HybridJava. That one looks rather consistent. |
||
|
|
|
|
Current timezone is GMT May 17, 2012 11:15:07 AM |
