[
https://issues.apache.org/jira/browse/TUSCANY-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707968#action_12707968
]
Ramkumar Ramalingam commented on TUSCANY-2962:
----------------------------------------------
Hi Scott,
As you have mentioned, the WSDL4J tries to process the WSDL as if its having
two distinct Operations.
In this case, we should be able to throw an exception by checking getMessage()
of the operation's input and output....
if (operation.getInput().getMessage() == null) {
throw error;
}
if (operation.getOutput().getMessage() == null) {
throw error;
}
I hope this will generate the required error message.
> Throw an exception if multiple same-name operations are detected by WSDL intf
> introspector
> ------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2962
> URL: https://issues.apache.org/jira/browse/TUSCANY-2962
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Reporter: Scott Kurz
> Assignee: Ramkumar Ramalingam
> Priority: Minor
> Attachments: MyMain.java, test.wsdl
>
>
> I noticed that a particular user error involving a badly-formed WSDL can be
> hard to debug.
> In my case (will attach example) I have the binding input/output @name not
> matching the portType input/output @name. Though wsimport has no problem
> generating Java compatible with my WSDL, the WSDL4J library processes my WSDL
> as having two distinct Operation(s) for my portType (will attach a sample
> program to show what I mean).
> Given the time it took me to realize what was going on later (I'll spare you
> the details), it seems a useful thing to do would have been for the WSDL
> introspector to flag this as an error instead of letting me go any further.
> Any issues with adding this type of validation?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
