Oxygen XML Forum

Hi !

I'm trying to add a Xalan extension to my XSL transformation using the procedure explained in the manual (and here as well), but it fails and returns the following error message :
There is of course a xalan.jar in this directory, so I'm not sure what's happening.

Can anyone help ?

Thanks in advance,

Gilles

Hi,

For some reason Oxygen seems to fail when loading the transformer from xalan.jar and it assumes the jar isn't there(it could be missing or broken).

Did you copy another version of Xalan(xalan.jar) to the Oxygen/lib directory?

Have you tried to run a transformation with Xalan with a fresh/clean scenario(no extensions configured)?
If it works without the extensions, make sure you haven't added the Xalan.jar to the extensions from the transformation scenario.

If all else fails, a solution would be to download Oxygen again and reinstall it(first uninstall and delete the directory of the previous installation to avoid leftovers).

Regards,
Adrian

Thanks for your quick reply !

See my answers below.

adrian wrote:Hi,

For some reason Oxygen seems to fail when loading the transformer from xalan.jar and it assumes the jar isn't there(it could be missing or broken).

Did you copy another version of Xalan(xalan.jar) to the Oxygen/lib directory?

No, I'm using the original jar bundled with <oXygen/>. I've already tried the latest Xalan bundle, but it didn't solve the problem.

adrian wrote: Have you tried to run a transformation with Xalan with a fresh/clean scenario(no extensions configured)?

I've just tried, and it does work with no extension. Could it be that the error message is misleading and that it actually fails when invoking the extension ?

adrian wrote: If it works without the extensions, make sure you haven't added the Xalan.jar to the extensions from the transformation scenario.

I haven't added the Xalan.jar to the extensions.

adrian wrote: If all else fails, a solution would be to download Oxygen again and reinstall it(first uninstall and delete the directory of the previous installation to avoid leftovers).

I kinda did that already, since I first faced the issue with the Eclipse plugin version, I thought I would give the standalone version a try, but it failed exactly the same way.

Hi,

Oxygen adds the extensions to the classpath when it creates the transformer(Xalan). It's possible that the extensions are interfering with the actual initialization of Xalan classes and Oxygen assumes the jar is not there.


If you want to enable logging in Oxygen to try and understand what happens, create a file named log4j.properties in the Oxygen installation directory with this content: Restart Oxygen, reproduce the problem and close Oxygen. You will find a directory named 'oxygenLog' on your Desktop and inside it the generated log files(oxygen.log.*). Please zip those files and send them to support@oxygenxml.com

Note that the file 'log4j.properties' triggers the debug mode which decreases the application performance severely. At the end of the procedure please do not forget to remove this file from the Oxygen installation directory.

Regards,
Adrian

I finally got it to work, thanks for your help !

It turns out I was the culprit : my jar contained a MANIFEST file with classpath entries and a main-class attribute, which apparently <oXygen/> didn't like very much.