On 4 Jun 2004, at 22:56, Frank Zammetti wrote:
<snip>
After that, I'm thinking that a .04 release maybe a week later seems reasonable, and with that my main goal is implementing the pre- and post-transformations suggested here. I haven't thought this through yet entirely, but what I think this amounts to is not much more than adding an xslt-in and xslt-out attributes to the mappings in webservices-config.xml that, if present will trigger processing of the incoming and outgoing XML via these transformations. The incoming side of things seems relatively straight-forward to me, but the outbound side I can't see as clearly right now because as it currently stands, a JSP renders the XML, so how can I run the resultant XML through an XSL transformation and return the result to the client? One possibility is a new class that would create the XML and THEN run it through the transformation. In addition to that, I would probably add an attribute to the <service> mappings that would specify whether a JSP is going to render the output, or it will be the result of a transformation. This is just rough thinking at the moment, at least as far as the outbound side goes.
1 if you want inspiration about pipelining, then take a look at cocoon: they've been successfully doing this kind of thing for years!
2 the problem with transformations is that (if you want to make them perform), the framework needs to be build with them in mind. typically, this means using something like a SAX pipeline.
3 using a SAX pipeline restricts the choice of object-xml binders that can be used. having a choice is object-xml binders is important.
4 IMHO the most elegant solution would be to replace the entire rendering layer (jsp's etc) with a configurable component-based object-xml lightweight binding framework. the actions take and produce objects which are then rendered to and from xml by the framework. any transformations should be done within this layer rather than without allowing different components to support them in different ways (or not at all).
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
