On Mar 7, 2016 7:55 AM, <sflo...@nc.rr.com> 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 library. Wrt Ant, we put Saxon in its lib path so we know it will get used since we have other programs outside of Ant invocation context that use Saxon. Puting it in the lib path avoids the need to explicitly designate the provider in the xslt task. --ewh
