I'm sure changing the Translet interface is going to be more feasible. I have no experience with xsltc internals but there are undoubtedly others here who know enough to say whether this is reasonable or not.
Geoff > -----Original Message----- > From: jcplerm [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 30, 2003 3:55 PM > To: [EMAIL PROTECTED] > Subject: Re: Shipping compiled translets rather than XSL files in plain > text format > > > Taking a look at XSLTC-related source files, it appears that > there is a limitation on XSLTC's side in terms of requiring > a DOM object as argument to the method "transform" of > class org.apache.xalan.xsltc.Translet. > > This is the Translet interface definition: > > package org.apache.xalan.xsltc; > public interface Translet { > public void transform(DOM document, TransletOutputHandler handler) > throws TransletException; > public void transform(DOM document, TransletOutputHandler[] handlers) > throws TransletException; > public void transform(DOM document, NodeIterator iterator, > TransletOutputHandler handler) > throws TransletException; > public Object addParameter(String name, Object value); > public void buildKeys(DOM document, NodeIterator iterator, > TransletOutputHandler handler, int root) > throws TransletException; > public void addAuxiliaryClass(Class auxClass); > public Class getAuxiliaryClass(String className); > public String[] getNamesArray(); > public String[] getNamespaceArray(); > } > > The fact that a DOM object is required limits its > applicability to the Cocoon framework, since one of the > biggest strengths of Cocoon is the SAX-based processing. > In order to take advantage of a Translet in a Cocoon pipeline, > a sitemap component would then have to first build a DOM tree from > the stream of SAX events and then invoke the translet. > Looks feasible, but a Translet should be able to handle SAX > events, in addition to a DOM document anyway. > > Then I guess there are two ways of moving ahead. > Please correct me if I'm wrong: > > 1) Have XSLTC's Translet implementation changed, > so it is able to deal with SAX-based processing; > > 2) Cocoon provides a way of compiling, or at least > serializing the stylesheets. This compiled or serialized > image of the pipeline transformations could then be > deployed at customer sites. This would then mean > Cocoon would be doing similar to XSLTC, but then > comes the question to Cocoon's developers: what is the > feasibility? > > Thanks, > > Julio > > ----- Original Message ----- > From: "Geoff Howard" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, March 30, 2003 6:42 AM > Subject: RE: Shipping compiled translets rather than XSL files in > plain text > format > > > > A great question I'd be interested in. I've not heard anyone > doing this, > so > > if you > > don't get an answer you'll need to dig into it yourself. The > first thing > > I'd try is > > to see how xsltc (I assume you're using that) handles precomiled > > stylesheets. What > > does it expect as its source? A classname? It may be as simple as > setting > > up > > cocoon to use xsltc (see archives and wiki) and passing the classname in > the > > src > > attribute of the transformer. > > > > Please report back what you find and I (or others) can help > evaluate what > > internal > > changes would be necessary to accomodate this if it doesn't just work > > automagically. > > > > Are you using 2.1dev or 2.0.4? > > > > Geoff Howard > > > > -----Original Message----- > > From: jcplerm [mailto:[EMAIL PROTECTED] > > Sent: Saturday, March 29, 2003 11:02 PM > > To: [EMAIL PROTECTED] > > Subject: Shipping compiled translets rather than XSL files in plain text > > format > > > > > > Is it possible to deploy Cocoon applications at customer sites just by > > installing compiled versions of XSL stylesheets (translets) rather than > > supplying them in plain text format? > > > > Thanks, > > > > Julio Lerm > > Chicago, IL > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]