 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | Spring and JSF | Spring and JSF 2005-07-07 - By Yagiz Erkan
Back
> The question I have, is anyone out there really using jsf for production
level code and what is the good, bad and ugly of using jsf now.
In one of the JavaOne technical sessions, Kevin Hinners (from Fedex)
talked about using JSF & Struts based on real-life case studies. One
of the three strategies is integration:
- Containment
- Rewrite
- Integration
Here's blog entry about this session:
http://www.groundside.com/blog/content/DuncanMills/J2EE%20Development/2005/06
/28/JavaOne_Tuesday_Stuts_to_JSF_conversion.html
There's a section about it in the TSS article under the header of
"Building the Compelling Case for JavaServer Faces":
http://www.theserverside.com/articles/article.tss?l=JavaOne_Day2
> Seems like I've been hearing a lot of hype about jsf for some time but not a
lot of real implementation in it. A lot of people seem to be playing with it
and talking about it and promising front ends that practically build themselves
. I'm wondering if the reality is catching up to the hype.
There are people using JSF but not as many as Struts :-) Currently
there are a few components vendors such as Isomorphic Software:
> Another thread indicated that some app servers support EJB 3.0? Have they
released the final spec? I went to their website this morning and it says that
it's in public review. So it's not really final yet that I can see. I wonder
how these implementations will vary from the final release of the spec. We
abandoned entity beans some time ago and we use hibernate but I don't think
session beans and MDB's are all that bad. I think they add a lot to our
application. I'm curious what other people have to say about that. With the new
spec, I believe they have fixed the entity bean problem. I'm curious what the
J2EE community will do with the idea of IOC that the spring framework brings.
Session beans and MDBs aren't gone. The "@(protected)" annotation on top
of your regular class makes it a Stateless Session bean class. You can
still use Hibernate (behind the new Java Persistence API) as the
persistence provider of your application. You can do dependency
injection using annotations like "@(protected), @(protected)". It's much much
better than EJB 2.x.
> With annotation in 1.5, it seems like the disadvantage of having half your
application in xml files is going away and therefore making some of my
objections to spring disappear.
That's exactly it. That's how I feel as well. The good thing about
annotations, they can still be overwritten in a descriptor/config
file.
- Yagiz -
==========================================================================To
unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
|
