[
https://issues.apache.org/jira/browse/TUSCANY-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708974#action_12708974
]
Scott Kurz commented on TUSCANY-2962:
-------------------------------------
Thanks Ram,
That seems like a definite improvement. Interesting that you decided not to
detect the error based on finding two similarly-named operations. I wonder
if there are any advantages to your way of doing it over mine, but I think
yours will definitely work to detect the error cases I had in mine.
> 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.
