You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/04/25 11:52:06 UTC

[jira] Commented: (TUSCANY-195) Load time EMF registering of URI to dynamic data object before static types can be registered.

    [ http://issues.apache.org/jira/browse/TUSCANY-195?page=comments#action_12376223 ] 

Jean-Sebastien Delfino commented on TUSCANY-195:
------------------------------------------------

Here's a hack to workaround this problem and get the WS interop tests to work:

in o.a.t.core.loader.assembly.ImportWSDLLoader, comment out lines 98 and 99:
                //XSDHelper xsdHelper = SDOUtil.createXSDHelper(context.getTypeHelper());
                //xsdHelper.define(xsdInputStream, null);

Defining the SDO metadata from the WSDL/XSD can be skipped if you have the generated SDO classes and call SDOUtil.registerStaticTypes(TheGeneratedFactory.class) as part of the initialization of one of your components.

This is just a temporary hack to unblock the WS testing (and it should help in the Bigbank scenario as well). This hack breaks other test cases which do not use static types (the TomcatIntegrationTestCases) so a clean fix needs to be provided for this bug ASAP, as most of us are blocked by it.


> Load time EMF registering of URI to dynamic data object before static types can be registered.
> ----------------------------------------------------------------------------------------------
>
>          Key: TUSCANY-195
>          URL: http://issues.apache.org/jira/browse/TUSCANY-195
>      Project: Tuscany
>         Type: Bug

>   Components: Java SCA Axis Binding
>  Environment: ALL current build
>     Reporter: Rick Rineholt
>     Priority: Blocker

>
> The loading of the TypeHelper in  ExternalWebServiceBuilder.createExternalWebServiceClient() line: 183 loads into the EMF registry the URI that most likely maps to a static generated type.  But this is occuring at load/build time prior to even any statically generated application SDO's are in scope. Or before they can be registered by the application.  This mapping is then done to DynamicDataObjects.  This results in a class cast exception when the generated interface expects the static types and a DDO is supplied.  My very limited understanding of EMF/SDO is that once the mapping is in place that subsequent registering of static types will not have any affect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira