[oXygen-sdk] FW: [oXygen-user] Save via WebDAV

[Oxygen XML Editor Support (Radu Coravu)]

HI Gary,

Unfortunately we do not have API to allow access to content inside the 
Results view.

We do have API to allow access to the opened documents in the main editor.

For example if you edit the transformation scenario and in the "Output" 
tab choose to uncheck "Present as a sequence" and choose to open the 
document in the editor, after the resulting document is opened in the 
editor we have APIs to get the contents of the opened document.

But once the result is opened in the editor you can also use the main 
menu File->Save to URL, choose to "Browse Data Source Explorer" and save 
it to the Exist connection.

Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 4/14/21 18:34, Gary Kopp wrote:
>
> Hello Radu. I’m pleased to see you’re still helping out with the 
> Oxygen SDK. We corresponding quite some time ago (on a different 
> subject that I ultimately abandoned) and you were very helpful.
>
> I don’t need an API to “control where and how a resource is saved.” 
> Since the eXist database is already accessible using the XMLRPC 
> interface exposed by an existing Oxygen datasource I could 
> theoretically write the results to eXist directly in Java code, _/if/_ 
> I trigger my plugin to run after manually executing an XQuery and (and 
> this is the key) the results of the XQuery are sitting around in 
> memory and can be addressed via an Oxygen SDK API. The results are 
> floating around somewhere in memory, since they are already displayed 
> in the results window. Am I making any sense?
>
> --Gary
>
> *From:* oXygen-user <oxygen-user-bounces at oxygenxml.com> *On Behalf Of 
> *Oxygen XML Editor Support (Radu Coravu)
> *Sent:* Wednesday, April 14, 2021 4:37 AM
> *To:* oxygen-user at oxygenxml.com
> *Subject:* Re: [oXygen-user] Save via WebDAV
>
> Hi Gary,
>
> Adrian asked me to help you further.
>
> I'm afraid using our Java APIs from a plugin we do not have control to 
> allow a third party plugin to control where and how a resource is saved.
>
> Maybe you can also look at other options Exist has for uploading 
> content to their database:
>
> http://exist-db.org/exist/apps/doc/uploading-files.xml 
> <http://exist-db.org/exist/apps/doc/uploading-files.xml>
>
> like the section about "Uploading files with XQuery". Or ask around on 
> the Exist list, maybe there are ways to set this up on the server side 
> instead of using Oxygen to drive the transformation.
>
> Regards,
>
> Radu
>
> Radu Coravu
> Oxygen XML Editor
>
> On 4/13/21 19:27, Gary Kopp wrote:
>
>     Thanks Adrian. Defining eXist WebDAV as a network drive is a great
>     option, and I’m embarrassed that I didn’t think of that – it’s
>     pretty obvious. If I want to take this to the next step (more
>     automation), do you know if transformation output/results are
>     API-accessible using the oXygen SDK?
>
>     --Gary
>
>     *From:* oXygen-user <oxygen-user-bounces at oxygenxml.com>
>     <mailto:oxygen-user-bounces at oxygenxml.com> *On Behalf Of *Oxygen
>     XML Editor Support (Adrian Buza)
>     *Sent:* Tuesday, April 13, 2021 7:36 AM
>     *To:* oxygen-user at oxygenxml.com <mailto:oxygen-user at oxygenxml.com>
>     *Subject:* Re: [oXygen-user] Save via WebDAV
>
>     Hi,
>
>     Both the results and/or output of an Oxygen transformation are
>     designed to be saved locally.
>     So, no, there is no way to configure an Oxygen transformation
>     scenario to output the result to a remote location (this includes
>     an eXist-db database).
>
>     One trick you can use, if you have WebDAV enabled on your eXist-db
>     server, is to mount the WebDAV repository as a network drive (or
>     as a folder for Linux/macOS) and configure Oxygen to output to
>     that mounted location (as if it was local).
>
>     Regards,
>     Adrian
>
>
>     Adrian Buza
>
>     oXygen XML Editor and Author Support
>
>     On 12.04.2021 00:01, Gary Kopp wrote:
>
>         I must be missing something … this is too complicated. I’m
>         using oXygen with eXist-db. All I want to do is save the
>         results of an XQuery query to the eXist database as a new
>         document in a direct a way as possible. Saving the results
>         from the results window only seems to support the local
>         filesystem. I can jump through a few hoops and get the results
>         transferred to an editing window where I can “Save to URI” and
>         ultimately get it sent out via WebDAV, but the dialogs for
>         that are ridiculously convoluted IMO. Am I missing a more
>         direct way?
>
>         --Gary Kopp
>
>
>
>
>         _______________________________________________
>
>         oXygen-user mailing list
>
>         oXygen-user at oxygenxml.com  <mailto:oXygen-user at oxygenxml.com>
>
>         https://www.oxygenxml.com/mailman/listinfo/oxygen-user  <https://www.oxygenxml.com/mailman/listinfo/oxygen-user>
>
>
>
>     _______________________________________________
>
>     oXygen-user mailing list
>
>     oXygen-user at oxygenxml.com  <mailto:oXygen-user at oxygenxml.com>
>
>     https://www.oxygenxml.com/mailman/listinfo/oxygen-user  <https://www.oxygenxml.com/mailman/listinfo/oxygen-user>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-sdk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20210415/cb177622/attachment.html>