If the classpath is not identical, you could get a different transform
provider. For example, we use Saxon as our provider, overriding what is
provided in the runtime library.
Thank you for the hint! I downloaded the latest xalan distribution and
executed the ant script with the "classpath" a
On Mar 7, 2016 7:55 AM, wrote:
>
> If you are using the same JVM and simply executing the XSL differently, I
don't see why not...
If the classpath is not identical, you could get a different transform
provider. For example, we use Saxon as our provider, overriding what is
provided in the runtime
Al,
It wasn't apparent to me why there'd be a difference...
If you are using the same JVM and simply executing the XSL differently, I don't
see why not...
I mean once you kick of the XSL I can't imagine there is something different in
running from Ant vs your Java app. I spent a number of ye
Hello Scot,
thanks for a quick response!
> first you are killing yourself in the way you XSLT is
> written
> [. . .]
> You are trying to do the work of the templating engine in your XSLT :)
Yes, I know this is a "procedural" way of doing things and maybe not the best.
But the example is just a
So a few things - first you are killing yourself in the way you XSLT is
written. Personally, I'd do:
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
