Hi Craig, >A completely different way to consider using JSF would be to build a RenderKit >that took input like this and generated the corresponding HTML (or whatever) >markup, starting from the exact same components as the standard HTML RenderKit. > In the JSF release, there is the very beginnings of an example how this can be >done, which uses XUL as the input templating language. Fleshing something like >this out could leverage the fact that Mozilla has already popularized this as a >technology for defining page layout, as well as some amount of interactivity.
I have a question here. I've been thinking of ways of how JSF and XSLT could be leveraged together, with or without leveraging JSP. Let's say we have an application where the Action classes make lots of calls to SOAP services and sometimes receive fairly large XML documents. In the case of large XML responses, converting the XML to POJOs may turn out to be unnecessary processing, where as you can simply do an XSLT transformation over the XML response to generate the final markup output. So what would be an efficient way to leverage both JSF and XSLT here? Could this be a good strategy: "Implement a RenderKit and JSF components that take XML documents as the business object input (instead of JavaBeans, Maps, etc.) and uses XSLT to generate the device-specific markup output. Then if you are using JSP as the templating system, implement a JSP taglib to call these components. If you're using another templating engine, write a tag library specific to that templating system and call your components." >Craig Mete --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
