[
https://wso2.org/jira/browse/MASHUP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451#action_16451
]
Keith Godwin Chapman commented on MASHUP-631:
---------------------------------------------
This is impossible to do cause rhino keeps the operations in a Map (whcih has
no notion of ordering). Also axis2 keeps the opeartions in a map (whcih has no
notion of ordering) so even if were to do some string manipulation and find out
the operation order from the service the WSDL will not show them in order
because of the way axis2 keeps operations.
> Reverse order of operations in generated WSDL
> ---------------------------------------------
>
> Key: MASHUP-631
> URL: https://wso2.org/jira/browse/MASHUP-631
> Project: WSO2 Mashup Server
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Priority: Minor
> Fix For: 1.1
>
>
> Currently, the order of functions in the mashup source is reversed in the
> WSDL2 operation order, and therefore in the ?doc and ?tryit. The order of
> operations in the source is generally significant, simple workflows can be
> indicated by specifying the "start" operation before the "stop" operation.
> Preserving this in the docs and try-it would be valuable.
> Note that a workaround can be added to the doc or tryit xslt but the more
> primary fix would be preferable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://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
