exist-db collections and xslt debugger

[majining]

Hello! This is my first post, and I apologize if this is not the proper sub-forum.

I have set up oxygen to be the front end for an eXist-db installation. It is up and running, but I am having a problem accessing some of my 'collections' (folders). Here is the issue:

In the oxygen Data Source Explorer panel, I created several New Collections. They all appear there without a problem. I then imported an xml file and an xslt file to the database. These also appear without a problem. However, when I switch to the XSLT debugger mode, some of my collections do not appear in the output file tree. That is, when I go to set the output to save a new file, I cannot find the collections that I created. Except(!) one of them does appear. I checked the write permissions, and they are identical, so I'm mystified as to why one of these would appear an the others don't. I figured there is a step I am missing to set the oxygen XSLT debugger to access the database, but that doesn't explain why one of the folders does appear.

In case it helps, here is what I'm trying to do: I want to have the XSLT debugger output files to the exist-db, in database 'collections' that I've created. If there is another way to do this, I'm all ears.

I would be very appreciative of any advice on this matter!
Thanks!
Scott

[adrian]

Hi,

Please note that the result of an XSLT transformation (also applies to an XSLT debugging session) can only be configured to be output locally (or a location mapped in the local file system). The 'Output' path must point to a file name (not a folder).
I'm not sure how one of the folders did appear in the database, unless it's also local and you pointed to its folder from the local file system.

There is a way to output it directly to the remote location if you use xsl:result-document (XSL 2.0) in your stylesheet, but you do have to use a custom URL that would probably work only in Oxygen.
In the Data Source Explorer create the output file in that collection, right click on it and use the 'Copy location' to obtain its URL. You can then set the @href of the xsl:result-document to point to that URL.

Regards,
Adrian