[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    [jira] Resolved: (WINK-229) JAXBXmlProvider should tolerate user
From:       "Mike Rheinheimer (JIRA)" <jira () apache ! org>
Date:       2009-11-09 17:25:32
Message-ID: 992071429.1257787532515.JavaMail.jira () brutus
[Download RAW message or body]


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

Mike Rheinheimer resolved WINK-229.
-----------------------------------

    Resolution: Fixed

Thanks Bryant.  Fixed in SVN 834150.  Also updated WINK-229_2.patch file here in the \
jira.

> 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
> 
> 
> 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.


[prev in list] [next in list] [prev in thread] [next in thread]