Craig McClanahan wrote:
With JSF, however, the situation is different. Every JSF component is, at its core, just a JavaBean ... it doesn't care what technology is used to ultimately manage the page. Yes, we provide JSP tag wrappers around all the standard components (because that addresses the need of a very large portion of the marketplace), but it's not required. The reason is that JSF provides a pluggable ViewHandler implementation ... the default one does RequestDispatcher.forward() calls (just like Struts does), making it very easy to use JSP, but this is by no means required.
You like Tapestry style separation of the component tree definition from the static HTML text? That's not hard ... go get Hans's JSF book and read the last chapter, to get you 80% of the way to a robust ViewHandler solution.
Maybe you'd prefer XForms? Go for it ... writing a ViewHandler that transforms your favorite way of representing a component tree into an XForms document is MMP (Merely a Matter of Programming :-).
Or, maybe you'd prefer an XML based solution that has all the component stuff in a single file, and you're contemplating an XSLT based solution that transforms component definitions into the corresponding HTML. Go for it. (Of, course, if you use the XML syntax for JSP pages plus JSF component tags, you get this pretty much for free ... oops, sorry, forgot you might be one of those that doesn't like JSP :-).
We're thinking about using Flash forms for some things. Will they plugin nicely to JSF?
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
