[ http://issues.apache.org/jira/browse/WSCOMMONS-78?page=comments#action_12432572 ] Jochen Wiedmann commented on WSCOMMONS-78: ------------------------------------------
In the meantime, I have detected that Axis 2 depends much, much more on these deprecated API's than I had expected. Unfortunately that means, that the serialization stuff in Axis 2 is most likely broken, at least if it depends on the same assumptions, which are implicit in the API. (Basically, it is assumed that all namespaces are declared in the top level elements, which is of course recommendable, but cannot be trusted.) I'll try to understand the serialization framework in Axis 2 first, before I'll continue my work. > Including a schema without namespace into a schema with namespace is not > possible > --------------------------------------------------------------------------------- > > Key: WSCOMMONS-78 > URL: http://issues.apache.org/jira/browse/WSCOMMONS-78 > Project: WS-Commons > Issue Type: Bug > Components: XmlSchema > Reporter: Jochen Wiedmann > Attachments: XmlSchema-include-handling.patch, > XmlSchema-Include-Without-Namespace.patch > > > The XML Schema specification states in "4.2.1 Assembling a schema for a > single target namespace from multiple schema definition documents": > 2 One of the following must be true: > ... > 2.3 SII has no targetNamespace [attribute] (but SII' does). > 3 The appropriate case among the following must be true: > ... > 3.2 If clause 2.3 above is satisfied, then the schema corresponding to the > <include>d item's parent <schema> must include not only definitions > or declarations corresponding to the appropriate members of its own > [children], but also components identical to all the - schema components- of > I, > except that anywhere the - absent- target namespace name would have > appeared, the - actual value- of the targetNamespace [attribute] of SII' is > used. > In particular, it replaces - absent- in the following places: > 3.2.1 The {target namespace} of named schema components, both at the top > level and (in the case of nested type definitions and nested attribute and > element declarations whose code was qualified) nested within definitions; > 3.2.2 The {namespace constraint} of a wildcard, whether negated or not; > In other words, it is possible to include a schema without namespace, as if > it had the namespace of the including schema. > Unfortunately this fails with XmlSchema, as the attached patch demonstrates. > The patch includes a simple test case and could be applied, if this bug is > fixed. > Suggested resolution, as realized in JaxMeXS: If such a schema is being > parsed, then mutable instances of QName should be created, which would always > return the target namespace of the schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
