Thanks Dims for the pointer! I quickly glanced at the implementation and it appears they transform the XML pipeline definition into an Ant file. Just as I guessed by looking at the language specification ;-)
By looking at the implementation, it appears that the way the components are connected together in a pipeline is through Input and Output objects. Through the interface of these classes you can obtain either Java input/output streams or Java Objects that contain the whole input to be processed or processed output. This is very different from what Cocoon uses internally, which is a stream of SAX events. I don't know whether the Sun implementation can be modified to use SAX internally, but it may be more difficult to compute dependencies between processing steps when the resources are not fully available. This problem is probably not easy to solve, but I may be wrong. I don't know what would be the value of this implementation to Cocoon. Probably the XML pipeline language may have some value, but I don't see it as a huge improvement over Cocoon's current sitemap definition language. Greetings, -- Ovidiu Predescu <[EMAIL PROTECTED]> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff) On Tue, 12 Mar 2002 10:50:56 -0800 (PST), Davanum Srinivas <[EMAIL PROTECTED]> wrote: > FYI. > > --- "Eve L. Maler" <[EMAIL PROTECTED]> wrote: > > Hello dims, > > > > You might be interested in taking a look at a sample implementation of > > Pipeline that we've just made available: > > > > http://www.sun.com/software/xml/developers/pipeline/ > > > > While we can't devote lots of resources to incorporating Pipeline into > > Cocoon2 ourselves right now, we'd be happy to learn what you think > > once you've taken a look at this implementation, and take it from > > there. One idea we like regarding "Pipeline design futures" is to use > > the predefined task semantics in the sitemap to help Pipeline's > > interoperability. > > > > Thanks, > > > > Eve > > > > > > ===== > Davanum Srinivas - http://xml.apache.org/~dims/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
