Hello, I just got back into xslt after a lengthy break. Here is a suggestion that may save some time (in my case a few hours of debugging) - especially when one starts xslt from scratch: Change the xsl:var auto-complete from: <xsl:variable name=""></xsl:variable> to <xsl:variable name=&quo...

Nope - I already have "Format and indent the document on open" checked - it still does not open.

Lines - they may very well be long - I have sent my xml to support.

Thanks,
Radu.

When I try to open a 3mb xml I see the progress bar going to the end - but the file never gets displayed. The only time I saw this file displayed in oxygen - it was after waiting for more than 20 mins for the debug perspective to come up... and then it was not usable - couldn't get xpath executed ag...

Never mind - one has to configure it in the transformation scenario - Transformer combo box - select Xalan.

Still it would have been nice to see what engine am I running in the Editor perspective.

Thanks,
Radu.

I can switch between Saxon and Xalan in debug perspective but not in the Editor perspective. In the Editor perspective I am given the combo box options MSXML.NET AND MSXML.40 - which is strange - because when I run I get the following Saxon error: SystemID: C:\Projects\GPS-POCS\p2p.poc\xslt\test.xsl...

Eclipse always produces - The input file does not exist or is not valid. When I validate document - Indeed - I am getting a: Message:XQuery module validation/execution is not supported. Please validate/execute the main XQuery file.] But transformation works just fine from Java/saxon in eclipse. And ...

Was able to generate documentation using 8.2 standalone, but still fails in eclipse plugin.

P.S. works too using xqdoc separately.

Hope this helps,
Radu

Version 8.2 Got an xquery file - somewhat complex - imports a couple mudules. Steps to reproduce: 1. Select xq file 2. Go to menu: XQuery | Generate Documentation 3. Re-select the xq file (reduntant step) 4. Generate Documentation. Get a error dialog saying: The input file does not exist or is not v...

Never mind good old:
works just fine.

Thanks again,
Radu.

Dan, Thanks for your reply. It makes sense. I still have a question - how do I configure the oxygen scenario to point the variable $legalcodesString to an xml file? I have tried adding a parameter as: $legalcodesString = ${cfd}/../xml/legalcodes.xml and still get the error: No value supplied for req...

I have the following fragment in my xquery file:

declare variable $legalcodes as document-node() external;

What do I do in Oxygen xml editor to configure this external variable to point to an xml file?

Thanks,
Radu Marian