August 2007 - oXygen-user - www.oxygenxml.com

validation and custom java extensions
by Hausherr, Jens 09 Aug '07

09 Aug '07

Hello, maybe I have missed it in the documentation: How do I register custom XSLT-extensions implemented in Java so that the editor stops complaining about not finding a matching function? The transform works fine if I register my Jar file as an extension so the error reported by the editor is a little annoying. Mit freundlichen Gruessen / Best Regards / Avec mes meilleures salutations Jens Hausherr Senior Consultant Tel: +49-178-8866-097 Fax: +49-178-998866-097 mailto: jens.hausherr(a)logicacmg.com <blocked::mailto:jens.hausherr@unilog.logicacmg.com> Unilog Avinci - a LogicaCMG company Am Sandtorkai 72 D-20457 Hamburg http://www.unilog-avinci.de <blocked::http://www.unilog-avinci.de/> Unilog Avinci GmbH Zettachring 4, 70567 Stuttgart Amtsgericht Stuttgart HRB 721369 Geschäftsführer: Torsten Straß / Eric Guyot / Rudolf Kuhn / Olaf Scholz / Thomas Elsner This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

xsl question
by Timothy Reaves 09 Aug '07

09 Aug '07

I have an issue I'm trying to resolve. When I perform an xslt transform in the XSLT Debugger, the output is what I expect. When I execute a transform with the command line: java org.apache.xalan.xslt.Process -in applications\InputTemplate.xml -xsl configxsl\transformer.xsl -out applications\Output.xml the output is not the same. In oXygen, I've specified InputTemplate.xml as the XML, transformer.xsl as the XSL (both open in buffers) and Xalan. The difference I'm seeing is that in the debugger, an XInclude is being included (the output window shows the combined document, and properly transformed. This is what I want). The output when run from the command line leaves the XInclude element alone, but otherwise properly transforms the document. So does oXygen just process in-memory? Is there a way to see the equivalent command line? Thanks.

2 2

Saxon xinclude processing of Xquery
by Christian Wittern 09 Aug '07

09 Aug '07

Dear Oxygen users, The Saxon documentation (http://www.saxonica.com/documentation/changes/intro/xinclude89.html) says that starting with Version 8.9 (Java implementation) there is support for xinclude processing for both XSLT and XQuery. Now, since Oxygen 8.2 already bundles Saxon B 8.9.0.3 and it runs on my Mac with Java 1.5, I assume it should be possible to tell Saxon to expand my xincludes for the query. However, I can't quite figure out if Oxygen has an option somewhere or, failing that, how I can pass a commandline argument for Saxon through the transformer. Any help appreciated, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

2 3

[bug] printing diagrams is broke
by Timothy Reaves 08 Aug '07

08 Aug '07

I went to print a diagram of a schema I have been working on. So I context-clicked and selected print. The dialog that pops up offers little real options (margin and orientation), so I just pressed OK and walked over to the printer. Where 24 pages of paper were waiting for me. So I'm left wondering what moron thought that was a good thing when designing the print system? What an incredible waste of paper. Plus, like I really have nothing better to do that tape 24 pages (it's a relatively small schema too) together. I'm a big fan of oXygen, and have converted several of my co-workers over to it. This is really the first time I've had to just scratch my head in wonder. For images, the print system should either constrain to a single page (the default), or ask what to do.

2 4

Failed to create InputSource
by Kai Mütz 06 Aug '07

06 Aug '07

Hi, I use oXygenxml 7.2 within Eclipse 3.2.1 and want to resolve a path to a XML schema file using a catalog file whiche I have registered in oxygen preferences. The verbose output tells me that oxygen resolves the systemid correctly (Resolved System: http://.... file://.....) but cannot load the schema file from the resolved location: Failed to create InputSource: file://.... The resolved location is definitly correct and points to a valid schema file. Can anyone help me? Regards, Kai

2 2