I'm starting to begin looking at JSF in part because of what I've read here on the Struts mailing list. i.e. Struts is embracing JSF, many developers see it as inevitable. I have some experience with Tapestry and Ruby on Rails so I'm excited about component frameworks. However, what I don't know, having just started learning JSF is how ready it is. I can't take wars developed in Java Studio Creator and deploy them to WebSphere (we use WebSpere where I work) and I'm not sure how it stacks up to Struts in terms of input validation, ease of integration with a business tier and Hibernate and other common J2EE issues. Can anyone with experience give me an idea if now is the time to jump in the water?
The reason I ask here is because of the nature of Struts creating new projects to extend and enhance the JSF API. I don't know (with that in mind) if that's a sign of JSF not being fully baked, or not being up to par with what most Struts users are used to. This is one of those situations where I want to pick the right horse. My experience has been that usually the open source solution is the better solution. See Ant, Struts, Spring, Hibernate, Tomcat as examples. So because of licensing and who created the reference implementation I'm naturally a little skeptical of JSF. Excited, but skeptical. Hopefully someone can fill me in or at least explain what holes Shale is meant to fill. Preston --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
