You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/01/14 08:22:59 UTC

[jira] Commented: (CAMEL-924) Xml factory in camel-xstream

    [ https://issues.apache.org/activemq/browse/CAMEL-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48687#action_48687 ] 

Willem Jiang commented on CAMEL-924:
------------------------------------

I think this issue will not  appear on JDK 1.5, since the stax API begin to be a part of JDK since 1.6.
Here are the algorithm of XMLOutputFactory.newInstance() method determines the specific XMLInputFactory implementation class to load by using the following lookup procedure:
   1. Use the javax.xml.stream.XMLOutputFactory system property.
   2. Use the lib/xml.stream.properties file in the JRE directory.
   3. Use the Services API, if available, to determine the classname by looking in the META-INF/services/javax.xml.stream.XMLOutputFactory files in jars available to the JRE.
   4. Use the platform default XMLOutputFactory instance.

Since Camel just call the XStream lib to do the job, there is no explicate camel way(through URI) to do that, 
so I suggest you set the XMLOutputFactoryImpl as you want through upper ways (I prefer the system property way more).

TODO We need to add this into Camel FAQ.

> Xml factory in camel-xstream
> ----------------------------
>
>                 Key: CAMEL-924
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-924
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-xstream
>    Affects Versions: 1.4.0
>            Reporter: Vadim Chekan
>            Assignee: Willem Jiang
>
> Related nabble:
> http://www.nabble.com/xstream-marshalling-td19542712s22882.html
> We need to fixate the xml writer created in camel-xstream via javax.xml.stream.XMLOutputFactory
> (we need xstream component in Jira).
> Otherwise factory falls into unpredictable writer and in case of com.sun.xml.internal.stream.XMLOutputFactoryImpl it refuses to work if file.encoding is set to something different then UTF-8.
> May be propert implementation would be to attempt to use com.ctc.wstx.stax.WstxOutputFactory and if it fails, then produce a warning and use whatever is available. 
> Also for those who know what they are doing we can provide a setting in camel context which factory to use.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.