Hi all,
Thanks for help, but I would have prefered using turbine built-in
services (easily upgradable)
I think it's a bug that has to be corrected (when some of us have enough
time), the more so as
the new XSLtransformer class is more powerful (xsl parameters, ...).
Any suggestions ?
Bye
Raoul
Siegfried Goeschl wrote:
Hi Raoul,
I implemented a cousin of XSLT service based on DOM4J - would this be
an option for you?
Cheers,
Siegfried Goeschl
rc wrote:
Thomas Vandahl wrote:
Hi Raoul,
this was a change of mine. The XSLT service of Turbine now uses URLs
and the ServletContext methods to access the .xsl-files. This is a
step to get Turbine to run from a .war-file.
In your case I'd suggest to change the include path to an absolute
URL such as "http://somehost/xsl/tools.xsl"; This should fix the
problem.
Bye, Thomas.
Hi,
I understand your objectives, but I can't use absolute constant url
in my xsl [EMAIL PROTECTED] path. I can
only use relatives or dynamic(servlet context) uris. But as you know,
we can't use dynamic data inside [EMAIL PROTECTED] values.
So, I'm always blocked on this point.
By
Raoul
---------------------------------------------------------------------
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]
