RE: Content-type and transforms (was RE: [PROPOSAL] Release v2.2.0 of Maverick)
"Schnitzer, Jeff" <[email protected]>
| Newsgroups | gmane.comp.web.maverick.general |
|---|---|
| Message-ID | <[email protected]> |
> From: jim moore [mailto:[email protected]] > > The nice about moving this functionality into the framework as opposed to > the individual transforms is that it gives some regularity--it is very > clear > when looking at the maverick.xml file what the output of each transform is > if necessary (no need to look at source code). Also, all existing > transforms > and views would work immediately without modification. It would be nice to be able to fix this so that everything works properly even if users don't specify a content-type for every step (something I doubt that most users will do consistently). The only downside is the API change, right? All of the existing transform types in CVS right now extend AbstractTransformStep. All I have to do is add the dummy setContentType() method to AbstractTransformStep in the core and it will be unnecessary to modify any of the optional packages. Sound better? :-) I like this approach - it enables SAX-generating steps to specify content-type just like text-generating steps (which can specify the content-type on the HttpServletRequest). Jeff Schnitzer [email protected] ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en [INVALID FOOTER]