Components with interfaces defined using interface.wsdl can't be used by
clients using interfaces
-------------------------------------------------------------------------------------------------
Key: TUSCANY-312
URL: http://issues.apache.org/jira/browse/TUSCANY-312
Project: Tuscany
Type: Bug
Reporter: ant elder
Priority: Blocker
Fix For: M1
This was originally reportted in TUSCANY-141 which has now been closed without
the problem really being fixed. This aspect of the problem kept getting passed
off to a string of other JIRAs, all of which have now also been resolved but
the problem remains. See: TUSCANY-124, TUSCANY-141, TUSCANY-173, TUSCANY-178,
TUSCANY-218
If you use interface.wsdl in a .componentType side file then Tuscany
dynamically genetrates a Java class for the WSDL portType and thats the
interface implemented by the proxy returned to a J2SE client . The client would
usually have pregened their own interface from the WSDL and will be using that,
so it will get a class cast exception.
I'm having this problem with a J2SE client but I expect it would also happen
with anything where a wire target is a component using interface.wsdl.
At a guess i'd say the code that dynamically gens the new interface needs to
first check if there's a class with the same name in the applications
classloader heirachy.
--
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
