@adrian Thank you so much for the workaround. Our silly company has this area locked down from the developers. We'll have to concentrate on getting the enterprise team to upgrade our baseline to oXygen 16 (or at least the JRE). As eXist 2.1 was working with the oXygen 12's java 1.6.0_18, I attempted...

We are using oXygen on Windows 7 (talking to our eXist on Linux) :shock: (Maybe we can use this to prompt the software group to get us upgraded.) We were are able to function with our eXist 2.1 servers. As a side note, we also noticed our oXygen 12.0 doesn't have the latest Saxon to support XQuery 3...

Whilst we have a maintenance license to cover us up through the current version of oXygen, our company is extremely delinquent in upgrading our baseline software. Therefore, we are currently running oXygen 12.0. We recently upgrade our development eXist server from eXist 2.1 to 2.2RC2. In oXygen, we...

Adrian the command line option worked great and showed me the issue. (IOU a beer at XMLPrague2013.)

Adrian I am using my personal details here, so it won't be listed under me. Our SMP has been active for years now and expires shortly. I wanted some how see if the "74 days" could be used as leverage to get our company to move quicker on our upgrades. I'll use the supplied email address fo...

We are currently running v12.2.

We currently have 74 "maintenance days left".

If we were to install v13.2 on day 75, would this version work with our SGN.

(I ask as our employer is extremely slow in upgrading software.)

Adrian I missed typed our version. We are v12.2 not v13.2. (I am having a extremely difficult time getting our employer to upgrade our systems even though we own v13.2, and it sits on the shelf ... grrrrr!)

Thank you Adrian. With v13.2, I am able to get very simple scenarios to work. As I get more complicated, it still continues to work via the command line, but oXygen is giving me an error like "F [Xalan] Failed to compile stylesheet. 3 errors detected." Is there a way for to see these error...

<?xml version='1.0'?> <!--See http://xml.apache.org/xalan-j/extensionslib.html#pipedocument--><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:pipe="http://xml.apache.org/xalan/PipeDocument" extension-element-prefixes="pipe"...

In the scenario editor, there is a pulldown selection on canned scenarios (e.g., Xalan, Saxon..., xsltproc). Is it possible to add others?

Another resource: XSLT Cookbook

I am using the Xalan PipeDocument extension in an XSLT. Calling it via the command line with the java.exe with oXygen "jre\bin\java.exe org.apache.xalan.xslt ..." -- it works fine for me. Within the oXygen environment, but I'm getting the error "The Properties object passed to the Ser...

I have a number of Java extensions I need to use with my XSL stylesheets. These extensions are in both JAR and CLASS files.

Can anyone offer any assistance?