[
https://issues.apache.org/jira/browse/TUSCANY-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480874
]
Raymond Feng commented on TUSCANY-1165:
---------------------------------------
There's a simple workaround: Make sure the <import.sdo> statements come before
the <component> definitions.
The current implementation depends on a fully-popluated SDO HelperContext from
<import.sdo> to introspect the SDO generated classes. It's not ideal. I'm
talking to SDO folks to see if they can generate SDO classes with markers so
that we can recognize the SDO classes without requiring the <import.sdo>
upfront.
The other thing is that we do too much and too early in the loading phase. As
you know, the StAX parsing is sequencial and we cannot look ahead. One of the
proposal we discussed on the ML is to split the loading into two phases: SCDL
parsing and artifact resolving. Hopefully it will help to fix this problem in a
complete way.
> Integration branch - Timing issue: incorrect dependency on order of Component
> loader and ImportSDOLoader within Composite loading
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-1165
> URL: https://issues.apache.org/jira/browse/TUSCANY-1165
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Kernel
> Affects Versions: Java-SCA-integration
> Reporter: Scott Kurz
>
> As referenced in this email:
> http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg15250.html
> The Java component loader's introspection of the DataTypes in a Java
> component impl using SDO data types does not successfully detect the SDO
> DataTypes. This is because the the SDODataBinding.introspect() method
> (called by DataBindingRegistryImpl.introspectType()) requires the
> ImportSDOLoader to have already run by that point.
> Something needs to be done but I'm not knowledgable enough now to suggest how
> to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
