Can you briefly explain why JSF has to be "customized" in order for WebSphere applications to use it? See http://www-106.ibm.com/developerworks/java/library/j-integrate/ that makes the case for this point of view.
If this seems untrue, then can you say (or does you book explain) how to incorporate JSF into a J2EE application even though you are using WebSphere?
Thanks in adanvce!
[ March 03, 2004: Message edited by: john prieur ]
As far as 'customizing' I think the main point that must be customized is in some cases the JSTL 1.0 jar file must be substituted for the JSTL 1.1 jar because of incompatibilities. I have tested my code on JBoss with Tomcat 4.1.x and 5.0.x and it ran fine using the deploy directions found with the JSF beta release.
One more quick thing. The article you posted about is on the old EA4 release and many of the ideas espoused in that article were incorporated in the struts-faces work so you can get most of what the article discusses out of the box with the beta and the latest version of the struts-faces stuff. I have not had a chance to try out tiles with JSF yet but the readme in the beta claims that its been tested and found to work.
Hope this helps!
Originally posted by Bill Dudney:
The book has a whole chapter on integrating JSF with J2EE where I walk through building an app in a two tier mode and three tier mode.... article you posted about is on the old EA4 release and many of the ideas espoused in that article were incorporated in the struts-faces work ...