incubator-wink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryant Luk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (WINK-229) JAXBXmlProvider should tolerate user jaxb contexts
Date Fri, 06 Nov 2009 23:48:32 GMT

    [ https://issues.apache.org/jira/browse/WINK-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774495#action_12774495
] 

Bryant Luk commented on WINK-229:
---------------------------------

I originally got a repeatable problem in my build environment but after adding:

{code}
    @Override
    public String getPropertiesFile() {
        return "META-INF/wink.properties";
    }
{code}

to the JettisonJAXBContextResolverTest, the test passed for me (JDK 1.6 this time).  If the
Jettison provider is auto-registered via wink-application, the reader is disabled.  The wink.properties
file disables the auto-registration allowing you to turn on the Jettison provider as a reader
before registration.  The reason the reader is disabled by default is because of a bug in
Jettison where malformed JSON may cause infinite loops.

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


Mime
View raw message