Oxygen XML Forum

Hello, I'd like to request support for STX in Oxygen, at least for being able to run STX transformations (not necessarily in a debugger). Oxygen could use Joost as a default implementation.

Thank you for your request. We logged it to our issue tracker.

There is no documentation about the API of the StDB debugger for integrating it in a debugger IDE. StDB is the only debugger library based on Joost. It is distributed as a jEdit plugin but the API is not documented.


Regards,
Sorin

[ I also asked about this via support email a couple of months back,
and I'ld also still like to see this. ]

StDB contains the jEdit specific plugin code as well as a command line debugger,
so that not what you need documented. ( although the source code might be
useful as an example. )
If you do what that, then you probably need to build from cvs sources rather than just downloading the jar file.

Joost itself has a net.sf.joost.trace package which contains the classes and interfaces for tracing, debugging and instrumenting the joost STX process.

There are java api docs for these packages in the source distribution:

https://sourceforge.net/project/showfil ... p_id=55258

Unfortunately, I haven't found an online version of the docs I can link to.
However, the raw comments that get extracted to javadocs in the build
process are visible in the browseable CVS archive:

http://joost.cvs.sourceforge.net/joost/ ... iew=markup

-- Steve Majewski / UVA Alderman Library

msqr wrote:Hello, I'd like to request support for STX in Oxygen, at least for being able to run STX transformations (not necessarily in a debugger). Oxygen could use Joost as a default implementation.

You can run joost transforms (without the debugger):

[1] You can set joost to be your JAXP XSLT transformer:
Drop the joost jar into oxygen's lib/ folder.
In 'transformation options' , set the value of system property
"javax.xml.transform.TransformerFactory" to :
"net.sf.joost.trax.TransformerFactoryImpl"
( You may also have to enter .stx into the 'File Types' preferences pane
and set it to use the XSL Editor so .stx files are recognized as a
'stylesheet' -- however, this may make editing them awkward. )
Then define a transformation scenario using JAXP ( which will call joost
as the transform engine. )

[2] You can also run joost as an external transform.
( see oxygen docs for how to set this. )

-- Steve Majewski / UVA Alderman Library

Hi Steve,

Thanks for all the useful information.
We already have this feature added to our enhancements list but there is not a definite time line for it.
I'll try to increase it's priority.

Regards,
Radu

I am looking for an STX editor and was hoping Oxygen supported it. But, I cannot find any reference to it in the help documentation.
By the lack of comments on this subject, I would presume that it is still not supported.
So, I was wondering if you knew of any STX editors out there that I could use to Edit and Test some STX code?

Thanks,
Mike

Radu wrote:Hi Steve,

Thanks for all the useful information.
We already have this feature added to our enhancements list but there is not a definite time line for it.
I'll try to increase it's priority.

Regards,
Radu

Hi Mike,

We do not yet have support for STX out of the box, it is planned for now for Oxygen 13 but I can give no guarantees.

But Oxygen is a generic XML editor so if you associate to the STX the STX XML Schema:
http://stx.cvs.sourceforge.net/viewvc/s ... nition.xsd

you will get content completion and validation support in Oxygen.

You can also try to process the STX using the suggestions which are given above in this very post.

Regards,
Radu

Wow, that worked well! Thanks for the link and the explanation. It took me a little while to get it all hooked up, but it worked! I looked in the HELP to see how to associate the schema, followed the instructions and it just worked. How do you do that? Your "content completion" works like no other xml editor that I have tried.

I copied some .stx code into a new file to test it and Oxygen detected ambiguity errors in the data dictionary. So, I don't know if it is some type of configuration issue in Oxygen, or if there truly are issues in .xsd.

Thanks so much,
Mike

Hi Mike,

All our content completion and validation support is based on the associated schema describing the structure of the XML.

About the encountered validation problem, you can write us on the support email address (support at oxygenxml dot com) and give us some samples and we can look into it.

Regards,
Radu

Radu has registered the bug with SourceForge.

mrmohr> 1.I am getting the following error when I open a .stx file using the > schema: stx-stylesheet-definition.xsd

Radu: I registered a bug to the STX issues list for this:
https://sourceforge.net/tracker/?func=d ... tid=511477
The stx-stylesheet-definition.xsd XML Schema can be fixed by removing the reference:
<xs:element ref="text"/>
at line 73.



Later,
Mike