Using Oracle XDK for transformation
Here should go questions about transforming XML with XSLT and FOP.
-
- Posts: 16
- Joined: Sun Nov 13, 2005 6:43 am
Using Oracle XDK for transformation
I'm trying to use Oracle XDK for JAXP transformation.
1) I copied xmlparserv2.jar into the lib directory of the plugin
2) I set the propery javax.xml.transform.TransformerFactory to oracle.xml.jaxp.JXSAXTransformerFactory
3 I added <library name="lib/xmlparserv2.jar"/> into plugin.xml runtime section as I'm using the Eclipse plugin and did eclipse -clean restart
When I run the transformation, I get the following error in the Problems pan
"Severity Description Resource In Folder Location Creation Time Id
2 org.apache.xerces.parsers.SAXParser my.xsl sample November 12, 2005 7:18:18 PM 50"
what am I missing?
Thanks
1) I copied xmlparserv2.jar into the lib directory of the plugin
2) I set the propery javax.xml.transform.TransformerFactory to oracle.xml.jaxp.JXSAXTransformerFactory
3 I added <library name="lib/xmlparserv2.jar"/> into plugin.xml runtime section as I'm using the Eclipse plugin and did eclipse -clean restart
When I run the transformation, I get the following error in the Problems pan
"Severity Description Resource In Folder Location Creation Time Id
2 org.apache.xerces.parsers.SAXParser my.xsl sample November 12, 2005 7:18:18 PM 50"
what am I missing?
Thanks
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
Hello,
The problem with the XSLT transformer included in the Oracle XDK kit is that it cannot work as a standard JAXP transformer because it expects that the XML parser used to parse the input is an Oracle parser no matter what is the class name set in the system property for JAXP parser factory. When the input source of the transformer is created with other XML parser than the Oracle one the transform operation ends with a ClassCast exception because the class of the parser is not loaded from the Oracle jar file. If I parse the input source with the Oracle XML parser the transformation works OK. That means the Oracle XSLT transformer cannot be configured as JAXP transformer in the current version of <oXygen/>.
We will look into the possibility of allowing the configuration of an Oracle parser in <oXygen/> when the Oracle transformer is set as JAXP transformer but it will not be implemented in the short term (3 months).
I hope it helps,
Sorin
The problem with the XSLT transformer included in the Oracle XDK kit is that it cannot work as a standard JAXP transformer because it expects that the XML parser used to parse the input is an Oracle parser no matter what is the class name set in the system property for JAXP parser factory. When the input source of the transformer is created with other XML parser than the Oracle one the transform operation ends with a ClassCast exception because the class of the parser is not loaded from the Oracle jar file. If I parse the input source with the Oracle XML parser the transformation works OK. That means the Oracle XSLT transformer cannot be configured as JAXP transformer in the current version of <oXygen/>.
We will look into the possibility of allowing the configuration of an Oracle parser in <oXygen/> when the Oracle transformer is set as JAXP transformer but it will not be implemented in the short term (3 months).
I hope it helps,
Sorin
-
- Posts: 16
- Joined: Sun Nov 13, 2005 6:43 am
Hello Sorin,
Thanks for the follow up and explanation. I really appreciate it. I like oxygen and look forward to be able to work with Oracle XDK in future
One way this can be managed is through the use of "command" scripts that XDK comes with for both windows and *nix. I have sen other commercial IDEs (Stylus Studio and XML Spy) make use of those with setting the path and classpath instead of direct JAXP integration - that way of integration even works with Saxon
Regards
Nilesh
Thanks for the follow up and explanation. I really appreciate it. I like oxygen and look forward to be able to work with Oracle XDK in future
One way this can be managed is through the use of "command" scripts that XDK comes with for both windows and *nix. I have sen other commercial IDEs (Stylus Studio and XML Spy) make use of those with setting the path and classpath instead of direct JAXP integration - that way of integration even works with Saxon
Regards
Nilesh
-
- Site Admin
- Posts: 2095
- Joined: Thu Jan 09, 2003 2:58 pm
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service