[
https://issues.apache.org/jira/browse/WINK-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768267#action_12768267
]
Nick Gallardo commented on WINK-219:
------------------------------------
{quote}
The best solution will be probably testing if the class can be handled. I'm not
sure if there is a way to check it using JAXB APIs.
{quote}
We had to go through considerable gymnastics to get down to a usable set of
classes in the JAX-WS support for Axis2. Here's a pointer to part of what we
had to do to determine whether a class was usable:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/message/databinding/JAXBContextFromClasses.java?view=markup
Specifically, the separate() and findBestSet() methods are the key. The net
is, if the class can be added to a JAXBContext, then the assumption is that the
class is usable for marshalling/unmarshalling.
This is an alternative to an exhaustive approach of checking the class'
hierarchy looking for JAXB annotations.
So... maybe that means we can assume that if the class is part of the
JAXBContext that we have, then the isWritable should pass? Maybe, but
something makes me uncomfortable with that approach.
> JAXBXmlProvider should be able to handle inherited types, since JAXB is able
> to handle them
> -------------------------------------------------------------------------------------------
>
> Key: WINK-219
> URL: https://issues.apache.org/jira/browse/WINK-219
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 0.2
> Reporter: Kaloyan Kolev
>
> Here is the issue which led to opening this one:
> https://issues.apache.org/jira/browse/WINK-218
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
