1 2 Previous Next 16 Replies Latest reply on May 5, 2006 11:29 PM by Anil Saldanha

    Handling of xml wildcards


      This discussion relates to http://jira.jboss.org/jira/browse/JBWS-434.

      Heiko wrote:

      ... it seems to be a fairly complex problem
      that requires changes at the marshalling and unmarshalling components.
      But we might aswell think about an intermediate solution to keep moving:

      a, We make it possible to deploy schemas and jaxrpc-mappings that include xml wildcards, but the current implementation simply skips processing of these elements. At least it shouldn't complain or throw exceptions. Which basically means, we silently don't support them at the time being.

      b, I do an implemention based on axis, which we probably may need for backporting reasons anyway. But this depends on the efforts and time it requires to get support for wildcards.

      AFAIK marshalling wildcards needs to be supported in order to be JAXRPC compliant, but Thomas may know more about this.
      If this is the case, then A is not an option anyway.

      Alexey wrote:

      I think we already have this. There is an option in the XercesXsMarshaller

      public void setIgnoreUnresolvedWildcard(boolean value)

      Heiko wrote:

      That doesn't seem to work with mapped elements that contain wildcard content, i.e.:

      <!-- Types and global elements -->
      <xs:complexType name="DeliveryType" mixed="true">
       <xs:any namespace="##any" processContents="lax"
       minOccurs="0" maxOccurs="unbounded" />
       <xs:attribute name="Mode" type="xs:anyURI" use="optional" />

      Adrain wrote:
      What is wrong with processContents="lax" or "skip"?

        1 2 Previous Next