[
https://issues.apache.org/jira/browse/AXIS2-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800977#action_12800977
]
Rich Scheuerle commented on AXIS2-4603:
---------------------------------------
Thanks for the suggestion, but there are two problems with that approach.
1) The JAXB Umarshaller works more efficiently if the XMLStreamReader from the
same vendor is used. Thus there is a need to access the original parser.
2) Adding an XOPEncodingStreamReader may be one solution for accessing
DataHandlers...but I believe that it also adds a buffering.
thanks,
Rich
> JAX-WS: JAXB Unmarshal code no longer has direct access to the required
> XMLStreamReader
> ---------------------------------------------------------------------------------------
>
> Key: AXIS2-4603
> URL: https://issues.apache.org/jira/browse/AXIS2-4603
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Background:
> The JAX-WS programming model uses JAX-B objects as the representation of user
> business data.
> The JAX-WS runtime in Axis2 is responsibile for building the JAXBContext and
> marshaling and umarshaling the JAX-B objects.
> The marshaling and unmarshaling includes marshaling and unmarshaling MTOM
> data.
> When unmarshaling JAXB, the streaming, non-cached parser (original
> XMLStreamReader) or cached XMLStreamReader (OMStaXWrapper) is used
> as the input XMLStreamReader for the JAXB unmarshal code.
> Problem:
> The Axiom implementation has been changed such that the non-cached parser is
> now wrapped by one or more other axiom wrappers or delegates.
> Failure to the access the original steaming parser has resulted in poorer
> performance in some cases when unmarshaling
> WSCommons-518 now exposes additional methods to access the original
> non-cached parser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
