[
https://issues.apache.org/jira/browse/WODEN-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598417#action_12598417
]
Lawrence Mandel commented on WODEN-185:
---------------------------------------
Any update? Was this issue resolved with the W3C?
> WSDL spec should prohibit multiple types elements
> -------------------------------------------------
>
> Key: WODEN-185
> URL: https://issues.apache.org/jira/browse/WODEN-185
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assignee: John Kaputin
>
> There is a potential problem of multiple wsdl:types elements in a
> wsdl:description. I think this is due to an omission in the W3C WSDL 2.0
> spec, so I will raise a bugzilla against the spec and hopefully the new W3C
> Web Services core working group will handle it as Errata.
> The problem is that the WSDL 2.0 spec does not prohibit multiple wsdl:types
> elements within a description. The spec does state (in plain old prose) that
> the wsdl:description may have only one wsdl:types element, but it doesn't
> define an assertion for this and the WSDL 2.0 schema does not enforce it
> either. So, we can't detect such an error during schema validation or
> assertion validation.
> Currently Woden will throw a 'duplicate types element' WSDLException if
> DescriptionElement.addTypesElement is called more than once. So if a
> wsdl:description element contains more than one wsdl:types element, then
> during parsing this exception will be thrown and parsing will stop. The
> preferred parsing behaviour of Woden is to parse the entire WSDL document,
> even if it has errors, then report the errors. That is, Woden should not stop
> parsing when it hits a WSDL error. However, it will now stop parsing if a
> wsdl:description element contains more than one wsdl:types element.
> This behaviour was implemented by JIRA WODEN-141. We could relax this
> behaviour to allow multiple TypesElements to be added to DescriptionElement
> (i.e. don't throw the exception), but we still need a schema rule or
> assertion to determine that the WSDL is invalid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
