[
http://wso2.org/jira/browse/MASHUP-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467#action_15467
]
Jonathan Marsh commented on MASHUP-356:
---------------------------------------
Need to test the behavior with the stub and try-it to see if there's a graceful
error or fallback or something more catastrophic.
> Check for clashes between "return" output parameter and input parameters
> -------------------------------------------------------------------------
>
> Key: MASHUP-356
> URL: http://wso2.org/jira/browse/MASHUP-356
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Fix For: 1.1
>
>
> > > By convention we name the javascript return value “return” and
> > > generate the schema and signature appropriately. But if someone uses
> > > the name “return” for an input parameter, the signature would have to
> > > change to an #inout in this case. Does that make sense or do you
> > think
> > > it would make for messy signatures in other languages?
> > >
> > I suppose it'd be better if you mapped it to "return" only if there are
> > no clashes. If there is a clash, prepend a "_" then rinse and repeat. I
> > think that's what an early version of the JAX-WS mapping for WSDL 2.0
> > did.
> Also need to check that the try-it doesn't have a hard-wired dependency on
> "return" but uses the value from the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
