the first step would be to tweak the XSLTProcessor interface to also accept a setURIResolver() from the sitemap. This is the only thing my hack does (but not from the sitemap, i override it manually). But if you could define a custom URIResolver(s) from the cocoon.xconf or sitemap.xmap and the transfromer(s) would hounour the entries it would make it easier to create custom resolvers without hacking the XSLTProcessorImpl(s).
mvh karl oie -----Original Message----- From: Luca Morandini [mailto:[EMAIL PROTECTED]] Sent: 6. desember 2001 15:07 To: [EMAIL PROTECTED] Subject: RE: Inserting / Comining XML data Diana, regarding performance issues... I don't know much about it :( Regarding the sentence "Now that Cocoon2 has a SAX-driven pipeline...", I beg to differ, since the pipeline is NOT SAX-driven. Yes, the sitemap is static, I mean, you cannot decide midway in a pipeline to choose a different path (say, a different stylesheet) based on SAX events. Anyhow, the creative use of "document()" could make a lot of things possible... I'll investigate this further. Best regards, --------------------------------------------- Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html --------------------------------------------- > -----Original Message----- > From: terracare [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 06, 2001 2:48 PM > To: [EMAIL PROTECTED] > Subject: Re: Inserting / Comining XML data > > > > I'm happy to know that someone is trying to avoid XSP. > > > > I dislike it for being too static, I'd rather prefer doing > everything via > > XSLT... as I'm currently struggling to do. > > This was my original approach with Cocoon1 -- trying to use XSLT for > everything -- but I read a number of posts that claimed better performance > with XSP so I minimized my use of XSLT for all but presentation purposes. > Now that Cocoon2 has a SAX-driven pipeline, and if we write > efficient XSLT, > is it correct to assume, generally, that the performance issue > with XSLT is > less of an issue now? > > Diana > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
