[OASIS Issue Tracker] Created: (WSCALENDAR-231) Text needed on theuse of xs:anyType in the schema

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Text needed on the use of xs:anyType in the schema
--------------------------------------------------

                 Key: WSCALENDAR-231
                 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-231
             Project: OASIS Web Services Calendar (WS-Calendar) TC
          Issue Type: Bug
          Components: spec
    Affects Versions: pr02
            Reporter: Michael Douglass
            Assignee: Toby Considine


The following comes from the BIAS spec: biasprofile-v1.0-csprd02

Additionally, the WSDL exposed by an implementation shall not contain instances of xsd:any, xsd:anyType, or xsd:anyAttribute; these instances must be replaced with explicit schema contents. An example is the XML complex type, InformationType, which has xsd:any as its only child. This type is used to represent implementation-specific input data and return data. The children of InformationType must be replaced with explicit content. Doing so removes the ability to transmit unexpected or arbitrary data. Also, it provides a clear definition of information that a client needs to provide to the server,or expect to receive,to optimally perform an operation.

This is also an issue for the SOAP service and its use of any.

In practice with JAXB the xs:any element doesn't work well. The returned type is

com.sun.org.apache.xerces.internal.dom.ElementNSImpl

Tried changing the XRD schema to use substitution groups - didn't work.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira