> Hi David, > (May I refer You like this) Sure. I've been called worse ;-) > Is it not the case that the JSF coexisting with JSP > pages is a little Comprehensive..
IMHO it is horrid. > Ok,as I don't know fully about JSF, do we have the POssibility to put > Complete end to the Client Side SCript. Well, I think there is an option (specified in web.xml) to disable javascript, but I haven't tried it so I don't know if it would work or not. And I think this only would apply to straight JSF (Sun RI or Myfaces), but probable would cause failures for tomahawk or tobago. > There are certain > event based > attributes in the JSF tags lke onchange which do not function > for me on the > text boxes. Well if you can share what you're doing and what you expect to have happen (but isn't happening), maybe we could help you with that. > Do Sun Micro Systems is Completely going to > refactor the JSP > part for the purpose of it's complicated Execution of JSF > +JSP..is it so. No, JSF+JSP are a bad combination, as outlined at http://www.onjava.com/pub/a/onjava/2004/06/09/jsf.html. AFAIK, JSP will not be refactored to provide better JSF integration, but I could be wrong (I don't keep up so much with the JSP roadmap). We're using facelets (https://facelets.dev.java.net/). Apache shale's clay module might be another choice, but I haven't used it. Either one matches the JSF rendering lifecycle so it doesn't have the inherent problems that JSF+JSP does. The downside is that you lose access to all of those cool open source JSP tag libraries :-(
