[ http://issues.apache.org/jira/browse/TUSCANY-195?page=comments#action_12376468 ]
ant elder commented on TUSCANY-195: ----------------------------------- This still does not work for me for WS entryPoints with complex types after the changes to support import.sdo. It does work for simple types, eg, Ricks account WS from BB, but the interop.service in the sandbox does not. Hopefully its just me doing something wrong, could someone else have a go and confirm if it works for them or not? > 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
