camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Yao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6343) Stax support for toggling namespace awareness
Date Tue, 07 May 2013 22:35:15 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevin Yao updated CAMEL-6343:
-----------------------------

    Attachment: StAXJAXBIteratorExpressionPatch.txt
                StAXBuilderPatch.txt

Patches
                
> Stax support for toggling namespace awareness
> ---------------------------------------------
>
>                 Key: CAMEL-6343
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6343
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-stax
>    Affects Versions: 2.11.0
>            Reporter: Kevin Yao
>         Attachments: StAXBuilderPatch.txt, StAXJAXBIteratorExpressionPatch.txt
>
>
> There is an issue with the default stax XMLEventReader that makes unmarshalling xml's
result in null values when the xml has a top-level namespace that defines a xmltype that does
not match the tag name of the object to be unmarshalled. With how camel-stax is written, the
only way around it is to change the source xml file, which seems like an unnecessary harsh
penalty for all the quirky xml files out there. Therefore, I propose a solution to have the
xml reader ignore namespaces and thereby making the reader a lot more flexible.
> With this feature, someone can just add a boolean to the stax method:
> .split(stax(Product.class, false))

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message