You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Rick Rineholt (JIRA)" <tu...@ws.apache.org> on 2006/04/05 22:34:43 UTC
[jira] Commented: (TUSCANY-78) Incorrect signatures on Java
interfaces dynamically generated from WSDL
[ http://issues.apache.org/jira/browse/TUSCANY-78?page=comments#action_12373424 ]
Rick Rineholt commented on TUSCANY-78:
--------------------------------------
I'm going to look at this some. Depending on what I determine I *may* either provide a fix or possible just enough of a hack to get big bank to work. As a side I changed bigbank to use some other types beyond string. (my mistake :-)
Alternatively it comes to mind is that I'm using in this scenario the wsdl to SDO maven plugin which generates my types and interfaces already so while I still can see the need to automataically gen this from WSDL I think there should still be a way to specify in the SCDL I think in the externalService/interface.wsdl element an attribute or a way to annotate which java interface to use instead of generating it dynamically from the WSDL.
> Incorrect signatures on Java interfaces dynamically generated from WSDL
> -----------------------------------------------------------------------
>
> Key: TUSCANY-78
> URL: http://issues.apache.org/jira/browse/TUSCANY-78
> Project: Tuscany
> Type: Bug
> Components: Java SCA Model
> Reporter: Jean-Sebastien Delfino
> Assignee: Jean-Sebastien Delfino
>
> The model implementation uses ASM to dynamically generate Java interfaces from WSDL portTypes if necessary (if a Java interface has not been generated at development time by WSDL2Java) . The signatures of the generated Java methods are currently incorrect (incorrect number of args and incorrect types). This generator should be changed to reuse the logic from WSDL2Java to determine the correct number of args and their types, in a way consistent with what you would get by using the WSDL2Java tool at development time.
--
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