[
https://issues.apache.org/jira/browse/WINK-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774601#action_12774601
]
Hudson commented on WINK-229:
-----------------------------
Integrated in Wink-Trunk-JDK1.6-itests #13 (See
[http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.6-itests/13/])
: fix incorrect namespace
: tolerate user's JAXBContext resolver
> JAXBXmlProvider should tolerate user jaxb contexts
> --------------------------------------------------
>
> Key: WINK-229
> URL: https://issues.apache.org/jira/browse/WINK-229
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Fix For: 1.1
>
> Attachments: WINK-229.patch, WINK-229_2.patch
>
>
> Ran into a sample that had an extra creator method in the ObjectFactory that
> returned a JAXBElement. When this method exists, and the jaxbcontext is
> created using the String signature in a user's JAXB context resolver, the
> unmarshaller will call the ObjectFactory method that returns the JAXBElement,
> and thus the provider will return a JAXBElement, which may not be the desired
> object for the resource -- this would result in an IllegalArgumentException:
> argument type mismatch when calling the resource method.
> See patch, with test. It'll make sense.
> Also, we don't have a good set of tests for the JAXBXmlProvider. The one
> included here in the patch is a good one to use for additional JAXB tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
