[
https://issues.apache.org/jira/browse/TUSCANY-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630616#action_12630616
]
Raymond Feng commented on TUSCANY-2346:
---------------------------------------
In the trunk code, we already do a bit more by adding referenced classes from
the generic types.
Is it a popular case that a JAXB object contains children from other
classloaders? If you have a real use case, it will help.
Introspecting the class graph is expensive. For the single classloader case,
adding the root class to the JAXBContext is good enough.
> weaks in databinding-jaxb plug-in
> ---------------------------------
>
> Key: TUSCANY-2346
> URL: https://issues.apache.org/jira/browse/TUSCANY-2346
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Data Binding Runtime, Java SCA OSGi Integration
> Affects Versions: Java-SCA-1.2
> Environment: databinding-jaxb, OSGi
> Reporter: Ivan Churkin
> Fix For: Java-SCA-Next
>
> Attachments: JAXBDataBinding.java, workspace.rar
>
>
> There is a JAXB feature to create JAXB context by specifying the whole array
> of all mapping classes. Tuscany databinding-jaxb plug-in unable to work with.
> As a result, when application uses SCA for transmitting objects created by
> specifying complex JAXB context it crashes.
> This plug-in (databinding-jaxb) creates context for marshalling on very
> simple way. It gets class of root object and asks for JAXB to create context
> by providing it. So it supports only simple/default JAXB contexts.
> Its suggested more sophisticated procedure.
> 1. try to use default/simple context
> 2. if it does not work, to collect all JAXB related classes used in instance
> object and its properties/subobjects by reflection and to create context by
> array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
