> -----Original Message----- > From: Robert Koberg [mailto:[EMAIL PROTECTED] > Sent: Friday, July 09, 2004 10:45 AM > To: [EMAIL PROTECTED] > Subject: Re: XSLTC and runtime xpath eval, Smart Transformer > > > Wolf, Chris (IT) wrote: > > >We would like to implement a library of reusable templates, > >and to do so, we don't want to hard code xpaths in the libaray > >templates, we want to pass in the xpath string and have it > dynamically > >evaluated. > > > >As for "server-side", I'm not sure what you mean -- we are processing > >everything on the server and returning HTML. > > > > > > Could you provide an example of what you are trying to do? > There really > should be no need to use dynamic XPath in a set of resusable > templates. >
We want to have a library of reusable templates, and be able to override portions of the implementation via apply-imports, so we don't want to use named templates. I will forward some more concrete examples later. Thanks. > What I meant by 'server-side' was that you can setParameter's on the > Transformer prior to the transformation and use the params to > direct the > flow through your templates. > > Or you could provide a simple base Source XML and use the document > function with a custom URIResolver that uses your dynamic XPath to > return the result you need from the appropriate Source. > > best, > -Rob > > >Thanks, > > > > -Chris > > > > > > > >>-----Original Message----- > >>From: Robert Koberg [mailto:[EMAIL PROTECTED] > >>Sent: Wednesday, July 07, 2004 4:10 PM > >>To: [EMAIL PROTECTED] > >>Subject: Re: XSLTC and runtime xpath eval, Smart Transformer > >> > >> > >>Why do you need to evaluate? > >> > >>Could you accomplish the same thing by getting the result > server-side > >>and either passing it in as a param or bringing it in with the > >>document() function? > >> > >>best, > >>-Rob > >> > >> > >>Wolf, Chris (IT) wrote: > >> > >> > >> > >>>We are using XSLTC exclusively, but now we want to implement > >>>more re-usable XSL code and in order to do so, it seems inevitable > >>>that runtime evaluation of xpath's is neccesary. This implies > >>>the use of the EXSL extension 'evaluate', which unfortunately, > >>>does not work and there is no expected fix (see bug #15553). > >>> > >>>What about using the xalan-java mechanism to directly invoke > >>>code such as "org.apache.xapth.XPathAPI.eval()" from XSLTC? > >>>Will that work? > >>> > >>>As an alternative, can we mix translet code and intrepretive > >>>mode of XSL to use the 'evaluate' function? The sparse > >>>documentation on "SmartTransfomer" implies this possiblity, > >>>but does not explain how. > >>> > >>>Thanks, > >>> > >>> Chris Wolf > >>>-------------------------------------------------------- > >>> > >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
