Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
Originally posted by Roy Ben Ami:
No problem![]()
Actually, if you can use only jsp and srvlets in your apps then there is no need to move to any of these frameworks.
I will try to make it a bit clearer:
Strut/JSF - These frameworks allow you to use a better way of developing web applications. They provide you with a better MVC model (model view controller) in creating the HTMl and JSP/Servlets pages.
If you are developing web applications then they are defintly worth looking at.
EGB/JBoss - The move to the entire EJB and EJB Container (Application Server versus Web Server) is a big change and make sure you really need it. If you don't need something to manage the transaction/secutity for you then you don't need th overhead of the entire App container or EJB at all.
However, in many cases, having the container take care of stuff for you, or wanting to have a remote application (like a client that connects to your server through RMI) then EJB is your choice.
Spring - This is an alternative to the EJB thing![]()
It allows you to do almost the same things with less complication and with any container. some say it is better, others don't and it is your call. Like i said i don't use it often.
Hibernate - This is a good alternative to the thing called Entity Beans in EJB. Like you said it allows much easier persistence and quite nice to use. In EJB 3.0 they took almost all the ideas from here.
These are mostly my opinions, and i'm sure that there are better explantions out there (from more knowledgable users) but hope i helped you a bit.
%
SCJP 1.4, SCWCD 1.3, SCBCD 1.3
Originally posted by Roger Chung-Wee:
This comparison is for the presentation layer. This still leaves unanswered questions like, "My app requires distribution, messaging and transactions, is Spring suitable?"
%
SCJP 1.4, SCWCD 1.3, SCBCD 1.3
Originally posted by Roger Chung-Wee:
By distribution I mean that EJB instances get distributed across multiple JVMs by the EJB server. (This is why there is an EJB programming restriction that static variables must be final in order to avoid inconsistencies across the JVMs.) I am not knowledgable about Spring, but I don't think that Spring provides this sort of distributed processing.
If JMS is used, then an EJB server is valuable in that it is compelled to support the JMS 1.1 spec (for a server which is compliant with the EJB 2.1 spec) and is always a JMS provider. But with Spring, as you say, a separate JMS server is needed.
%
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
Originally posted by Dave Brown:
Does this mean it would be difficult/impossible to scale an application utilising Spring across several servers if the need arose ?
%
Regards, Dave Brown
SCJP 6 - [url]http://www.dbws.net/[/url] - Check out Grails Forum
You save more money with a clothesline than dozens of light bulb purchases. Tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
|