Loading ...
Sorry, an error occurred while loading the content.
 

Help: WS-I doc/lit with anyType SOAPBody

Expand Messages
  • Question Simple
    Hi All, I am writing a doc/lit web services, in which the elements under SOAPBody is unknown. That is, these two message are acceptable. 1.
    Message 1 of 9 , Mar 7, 2005
      Hi All,
       
        I am writing a doc/lit web services, in which the elements under SOAPBody is unknown. That is, these two message are acceptable.
       
      1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
      2. <SOAP-ENV:Body><Tag2><Tag3>It is also ok</Tag3></Tag2></SOAP-ENV:Body>
       
        The question is, if I write the wsdl as follows (pls refer to the attached file)
       
      <wsdl:message name="DataServiceRequest"/>
          <wsdl:message name="DataServiceResponse">
              <wsdl:part element="tns:DataServiceResponse" name="DataServiceResponse"/>
          </wsdl:message>
      ...
       
          <wsdl:portType name="DataServicePortType">
              <wsdl:operation name="DataService">
                  <wsdl:input message="tns:DataServiceRequest"/>
                  <wsdl:output message="tns:DataServiceResponse"/>
              </wsdl:operation>
          </wsdl:portType>
       
        it will assume that the request message is empty, instead of anyType. However, I cannot create an element with type=xsd:anyType since the element name will be appear under SOAPBody. Therefore, what should I do?
       
        I would also like the wsdl to be ws-i complaince, is it possible to do so?
       
      Cheers,
      Sonna Nach



      Yahoo! 工具列 - 內置防止彈出視窗工能
    • Anne Thomas Manes
      Try this: Anne On Tue, 8 Mar 2005 11:24:25
      Message 2 of 9 , Mar 8, 2005
        Try this:

        <wsdl:message name="DataServiceRequest">
        <wsdl:part element="xsd:any" name="DataServiceRequest"/>
        </wsdl:message>

        Anne


        On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
        <question_simple@...> wrote:
        >
        >
        > Hi All,
        >
        > I am writing a doc/lit web services, in which the elements under SOAPBody
        > is unknown. That is, these two message are acceptable.
        >
        > 1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
        >
        > 2. <SOAP-ENV:Body><Tag2><Tag3>It is also ok</Tag3></Tag2></SOAP-ENV:Body>
        >
        > The question is, if I write the wsdl as follows (pls refer to the attached
        > file)
        >
        > <wsdl:message name="DataServiceRequest"/>
        > <wsdl:message name="DataServiceResponse">
        > <wsdl:part element="tns:DataServiceResponse"
        > name="DataServiceResponse"/>
        > </wsdl:message>
        > ...
        >
        > <wsdl:portType name="DataServicePortType">
        > <wsdl:operation name="DataService">
        > <wsdl:input message="tns:DataServiceRequest"/>
        > <wsdl:output message="tns:DataServiceResponse"/>
        > </wsdl:operation>
        > </wsdl:portType>
        >
        > it will assume that the request message is empty, instead of anyType.
        > However, I cannot create an element with type=xsd:anyType since the element
        > name will be appear under SOAPBody. Therefore, what should I do?
        >
        > I would also like the wsdl to be ws-i complaince, is it possible to do so?
        >
        > Cheers,
        > Sonna Nach
        >
        >
        > ________________________________
        > Yahoo! 工具列 - 內置防止彈出視窗工能!
        >
        >
        > -----------------------------------------------------------------
        > This group is a forum for the discussion of the WSDL specification and its
        > implementation. Please stay on-topic.
        >
        >
        >
        > Yahoo! Groups Sponsor
        >
        > ADVERTISEMENT
        >
        >
        > ________________________________
        > Yahoo! Groups Links
        >
        >
        > To visit your group on the web, go to:
        > http://groups.yahoo.com/group/wsdl/
        >
        > To unsubscribe from this group, send an email to:
        > wsdl-unsubscribe@yahoogroups.com
        >
        > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
        >
        >
        >
      • question_simple
        Hi, Thanks for your solution. However, it is not ws-i basic profile 1.1 compliance as it violates R2206 (http://www.ws-
        Message 3 of 9 , Mar 8, 2005
          Hi,

          Thanks for your solution. However, it is not ws-i basic profile 1.1
          compliance as it violates R2206 (http://www.ws-
          i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
          possible to make it ws-i compliance?

          Sonna Nach

          --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
          > Try this:
          >
          > <wsdl:message name="DataServiceRequest">
          > <wsdl:part element="xsd:any" name="DataServiceRequest"/>
          > </wsdl:message>
          >
          > Anne
          >
          >
          > On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
          > <question_simple@y...> wrote:
          > >
          > >
          > > Hi All,
          > >
          > > I am writing a doc/lit web services, in which the elements
          under SOAPBody
          > > is unknown. That is, these two message are acceptable.
          > >
          > > 1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
          > >
          > > 2. <SOAP-ENV:Body><Tag2><Tag3>It is also ok</Tag3></Tag2></SOAP-
          ENV:Body>
          > >
          > > The question is, if I write the wsdl as follows (pls refer to
          the attached
          > > file)
          > >
          > > <wsdl:message name="DataServiceRequest"/>
          > > <wsdl:message name="DataServiceResponse">
          > > <wsdl:part element="tns:DataServiceResponse"
          > > name="DataServiceResponse"/>
          > > </wsdl:message>
          > > ...
          > >
          > > <wsdl:portType name="DataServicePortType">
          > > <wsdl:operation name="DataService">
          > > <wsdl:input message="tns:DataServiceRequest"/>
          > > <wsdl:output message="tns:DataServiceResponse"/>
          > > </wsdl:operation>
          > > </wsdl:portType>
          > >
          > > it will assume that the request message is empty, instead of
          anyType.
          > > However, I cannot create an element with type=xsd:anyType since
          the element
          > > name will be appear under SOAPBody. Therefore, what should I do?
          > >
          > > I would also like the wsdl to be ws-i complaince, is it
          possible to do so?
          > >
          > > Cheers,
          > > Sonna Nach
          > >
          > >
          > > ________________________________
          > > Yahoo! 工具??- ?§ç½®?²æ­¢å½ˆå‡ºè¦–ç?工能ï¼?> >
          > >
          > > -----------------------------------------------------------------
          > > This group is a forum for the discussion of the WSDL
          specification and its
          > > implementation. Please stay on-topic.
          > >
          > >
          > >
          > > Yahoo! Groups Sponsor
          > >
          > > ADVERTISEMENT
          > >
          > >
          > > ________________________________
          > > Yahoo! Groups Links
          > >
          > >
          > > To visit your group on the web, go to:
          > > http://groups.yahoo.com/group/wsdl/
          > >
          > > To unsubscribe from this group, send an email to:
          > > wsdl-unsubscribe@yahoogroups.com
          > >
          > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
          Service.
          > >
          > >
          > >
        • Anne Thomas Manes
          No -- it s impossible to make this scenario WS-I compliant. WS-I requires that the input message must provide a unique signature. The only way to make it WS-I
          Message 4 of 9 , Mar 9, 2005
            No -- it's impossible to make this scenario WS-I compliant. WS-I
            requires that the input message must provide a unique signature. The
            only way to make it WS-I compliant is to use a wrapper element.

            <xsd:element name="tns:DataServiceRequest">
            <xsd:complexType>
            <xsd:sequence>
            <xsd:any/>
            </xsd:sequence>
            </xsd:complexType>
            </xsd:element>

            <wsdl:message name="DataServiceRequest">
            <wsdl:part element="tns:DataServiceRequest" name="DataServiceRequest"/>
            </wsdl:message>

            But this approach would produce messages like this:

            <SOAP-ENV:Body>
            <tns:DataServiceRequest>
            <Tag1>It is ok</Tag1>
            </tns:DataServiceRequest>
            </SOAP-ENV:Body>

            or

            <SOAP-ENV:Body>
            <tns:DataServiceRequest>
            <Tag2>
            <Tag3>It is also ok</Tag3>
            </Tag2>
            </tns:DataServiceRequest>
            </SOAP-ENV:Body>

            Anne

            On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
            <question_simple@...> wrote:
            >
            >
            > Hi,
            >
            > Thanks for your solution. However, it is not ws-i basic profile 1.1
            > compliance as it violates R2206 (http://www.ws-
            > i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
            > possible to make it ws-i compliance?
            >
            > Sonna Nach
            >
            > --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
            > > Try this:
            > >
            > > <wsdl:message name="DataServiceRequest">
            > > <wsdl:part element="xsd:any" name="DataServiceRequest"/>
            > > </wsdl:message>
            > >
            > > Anne
            > >
            > >
            > > On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
            > > <question_simple@y...> wrote:
            > > >
            > > >
            > > > Hi All,
            > > >
            > > > I am writing a doc/lit web services, in which the elements
            > under SOAPBody
            > > > is unknown. That is, these two message are acceptable.
            > > >
            > > > 1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
            > > >
            > > > 2. <SOAP-ENV:Body><Tag2><Tag3>It is also ok</Tag3></Tag2></SOAP-
            > ENV:Body>
            > > >
            > > > The question is, if I write the wsdl as follows (pls refer to
            > the attached
            > > > file)
            > > >
            > > > <wsdl:message name="DataServiceRequest"/>
            > > > <wsdl:message name="DataServiceResponse">
            > > > <wsdl:part element="tns:DataServiceResponse"
            > > > name="DataServiceResponse"/>
            > > > </wsdl:message>
            > > > ...
            > > >
            > > > <wsdl:portType name="DataServicePortType">
            > > > <wsdl:operation name="DataService">
            > > > <wsdl:input message="tns:DataServiceRequest"/>
            > > > <wsdl:output message="tns:DataServiceResponse"/>
            > > > </wsdl:operation>
            > > > </wsdl:portType>
            > > >
            > > > it will assume that the request message is empty, instead of
            > anyType.
            > > > However, I cannot create an element with type=xsd:anyType since
            > the element
            > > > name will be appear under SOAPBody. Therefore, what should I do?
            > > >
            > > > I would also like the wsdl to be ws-i complaince, is it
            > possible to do so?
            > > >
            > > > Cheers,
            > > > Sonna Nach
            > > >
            > > >
            > > > ________________________________
            > > > Yahoo! 工具??- ?§ç½®?²æ­¢å½ˆå‡ºè¦–ç?工能ï¼?> >
            > > >
            > > > -----------------------------------------------------------------
            > > > This group is a forum for the discussion of the WSDL
            > specification and its
            > > > implementation. Please stay on-topic.
            > > >
            > > >
            > > >
            > > > Yahoo! Groups Sponsor
            > > >
            > > > ADVERTISEMENT
            > > >
            > > >
            > > > ________________________________
            > > > Yahoo! Groups Links
            > > >
            > > >
            > > > To visit your group on the web, go to:
            > > > http://groups.yahoo.com/group/wsdl/
            > > >
            > > > To unsubscribe from this group, send an email to:
            > > > wsdl-unsubscribe@yahoogroups.com
            > > >
            > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
            > Service.
            > > >
            > > >
            > > >
            >
            > -----------------------------------------------------------------
            > This group is a forum for the discussion of the WSDL specification and its implementation. Please stay on-topic.
            > Yahoo! Groups Links
            >
            >
            >
            >
            >
          • question_simple
            Thank you very much. Is there any tool which can check the validity of soap message against the wsdl? ... name= DataServiceRequest / ... 1.1 ...
            Message 5 of 9 , Mar 9, 2005
              Thank you very much. Is there any tool which can check the validity
              of soap message against the wsdl?

              --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
              > No -- it's impossible to make this scenario WS-I compliant. WS-I
              > requires that the input message must provide a unique signature. The
              > only way to make it WS-I compliant is to use a wrapper element.
              >
              > <xsd:element name="tns:DataServiceRequest">
              > <xsd:complexType>
              > <xsd:sequence>
              > <xsd:any/>
              > </xsd:sequence>
              > </xsd:complexType>
              > </xsd:element>
              >
              > <wsdl:message name="DataServiceRequest">
              > <wsdl:part element="tns:DataServiceRequest"
              name="DataServiceRequest"/>
              > </wsdl:message>
              >
              > But this approach would produce messages like this:
              >
              > <SOAP-ENV:Body>
              > <tns:DataServiceRequest>
              > <Tag1>It is ok</Tag1>
              > </tns:DataServiceRequest>
              > </SOAP-ENV:Body>
              >
              > or
              >
              > <SOAP-ENV:Body>
              > <tns:DataServiceRequest>
              > <Tag2>
              > <Tag3>It is also ok</Tag3>
              > </Tag2>
              > </tns:DataServiceRequest>
              > </SOAP-ENV:Body>
              >
              > Anne
              >
              > On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
              > <question_simple@y...> wrote:
              > >
              > >
              > > Hi,
              > >
              > > Thanks for your solution. However, it is not ws-i basic profile
              1.1
              > > compliance as it violates R2206 (http://www.ws-
              > > i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
              > > possible to make it ws-i compliance?
              > >
              > > Sonna Nach
              > >
              > > --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
              wrote:
              > > > Try this:
              > > >
              > > > <wsdl:message name="DataServiceRequest">
              > > > <wsdl:part element="xsd:any" name="DataServiceRequest"/>
              > > > </wsdl:message>
              > > >
              > > > Anne
              > > >
              > > >
              > > > On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
              > > > <question_simple@y...> wrote:
              > > > >
              > > > >
              > > > > Hi All,
              > > > >
              > > > > I am writing a doc/lit web services, in which the elements
              > > under SOAPBody
              > > > > is unknown. That is, these two message are acceptable.
              > > > >
              > > > > 1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
              > > > >
              > > > > 2. <SOAP-ENV:Body><Tag2><Tag3>It is also
              ok</Tag3></Tag2></SOAP-
              > > ENV:Body>
              > > > >
              > > > > The question is, if I write the wsdl as follows (pls refer
              to
              > > the attached
              > > > > file)
              > > > >
              > > > > <wsdl:message name="DataServiceRequest"/>
              > > > > <wsdl:message name="DataServiceResponse">
              > > > > <wsdl:part element="tns:DataServiceResponse"
              > > > > name="DataServiceResponse"/>
              > > > > </wsdl:message>
              > > > > ...
              > > > >
              > > > > <wsdl:portType name="DataServicePortType">
              > > > > <wsdl:operation name="DataService">
              > > > > <wsdl:input message="tns:DataServiceRequest"/>
              > > > > <wsdl:output message="tns:DataServiceResponse"/>
              > > > > </wsdl:operation>
              > > > > </wsdl:portType>
              > > > >
              > > > > it will assume that the request message is empty, instead of
              > > anyType.
              > > > > However, I cannot create an element with type=xsd:anyType
              since
              > > the element
              > > > > name will be appear under SOAPBody. Therefore, what should I
              do?
              > > > >
              > > > > I would also like the wsdl to be ws-i complaince, is it
              > > possible to do so?
              > > > >
              > > > > Cheers,
              > > > > Sonna Nach
              > > > >
              > > > >
              > > > > ________________________________
              > > > > Yahoo! €?å·¥å?€?¦Â??- ?€?§ç½®?€
              ?²æ­¢å½?€?Ã¥?€?¡ÂºÃ¨Â¦â?'³?€?Ã¥
              €?ᴏ?€?½ï¼?> >
              > > > >
              > > > > -------------------------------------------------------------
              ----
              > > > > This group is a forum for the discussion of the WSDL
              > > specification and its
              > > > > implementation. Please stay on-topic.
              > > > >
              > > > >
              > > > >
              > > > > Yahoo! Groups Sponsor
              > > > >
              > > > > ADVERTISEMENT
              > > > >
              > > > >
              > > > > ________________________________
              > > > > Yahoo! Groups Links
              > > > >
              > > > >
              > > > > To visit your group on the web, go to:
              > > > > http://groups.yahoo.com/group/wsdl/
              > > > >
              > > > > To unsubscribe from this group, send an email to:
              > > > > wsdl-unsubscribe@yahoogroups.com
              > > > >
              > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
              > > Service.
              > > > >
              > > > >
              > > > >
              > >
              > > -----------------------------------------------------------------
              > > This group is a forum for the discussion of the WSDL
              specification and its implementation. Please stay on-topic.
              > > Yahoo! Groups Links
              > >
              > >
              > >
              > >
              > >
            • Anne Thomas Manes
              You can use any schema validator to validate the contents of the SOAP body. On Thu, 10 Mar 2005 06:04:28 -0000, question_simple
              Message 6 of 9 , Mar 10, 2005
                You can use any schema validator to validate the contents of the SOAP body.


                On Thu, 10 Mar 2005 06:04:28 -0000, question_simple
                <question_simple@...> wrote:
                >
                >
                > Thank you very much. Is there any tool which can check the validity
                > of soap message against the wsdl?
                >
                > --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
                > > No -- it's impossible to make this scenario WS-I compliant. WS-I
                > > requires that the input message must provide a unique signature. The
                > > only way to make it WS-I compliant is to use a wrapper element.
                > >
                > > <xsd:element name="tns:DataServiceRequest">
                > > <xsd:complexType>
                > > <xsd:sequence>
                > > <xsd:any/>
                > > </xsd:sequence>
                > > </xsd:complexType>
                > > </xsd:element>
                > >
                > > <wsdl:message name="DataServiceRequest">
                > > <wsdl:part element="tns:DataServiceRequest"
                > name="DataServiceRequest"/>
                > > </wsdl:message>
                > >
                > > But this approach would produce messages like this:
                > >
                > > <SOAP-ENV:Body>
                > > <tns:DataServiceRequest>
                > > <Tag1>It is ok</Tag1>
                > > </tns:DataServiceRequest>
                > > </SOAP-ENV:Body>
                > >
                > > or
                > >
                > > <SOAP-ENV:Body>
                > > <tns:DataServiceRequest>
                > > <Tag2>
                > > <Tag3>It is also ok</Tag3>
                > > </Tag2>
                > > </tns:DataServiceRequest>
                > > </SOAP-ENV:Body>
                > >
                > > Anne
                > >
                > > On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
                > > <question_simple@y...> wrote:
                > > >
                > > >
                > > > Hi,
                > > >
                > > > Thanks for your solution. However, it is not ws-i basic profile
                > 1.1
                > > > compliance as it violates R2206 (http://www.ws-
                > > > i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
                > > > possible to make it ws-i compliance?
                > > >
                > > > Sonna Nach
                > > >
                > > > --- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
                > wrote:
                > > > > Try this:
                > > > >
                > > > > <wsdl:message name="DataServiceRequest">
                > > > > <wsdl:part element="xsd:any" name="DataServiceRequest"/>
                > > > > </wsdl:message>
                > > > >
                > > > > Anne
                > > > >
                > > > >
                > > > > On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
                > > > > <question_simple@y...> wrote:
                > > > > >
                > > > > >
                > > > > > Hi All,
                > > > > >
                > > > > > I am writing a doc/lit web services, in which the elements
                > > > under SOAPBody
                > > > > > is unknown. That is, these two message are acceptable.
                > > > > >
                > > > > > 1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
                > > > > >
                > > > > > 2. <SOAP-ENV:Body><Tag2><Tag3>It is also
                > ok</Tag3></Tag2></SOAP-
                > > > ENV:Body>
                > > > > >
                > > > > > The question is, if I write the wsdl as follows (pls refer
                > to
                > > > the attached
                > > > > > file)
                > > > > >
                > > > > > <wsdl:message name="DataServiceRequest"/>
                > > > > > <wsdl:message name="DataServiceResponse">
                > > > > > <wsdl:part element="tns:DataServiceResponse"
                > > > > > name="DataServiceResponse"/>
                > > > > > </wsdl:message>
                > > > > > ...
                > > > > >
                > > > > > <wsdl:portType name="DataServicePortType">
                > > > > > <wsdl:operation name="DataService">
                > > > > > <wsdl:input message="tns:DataServiceRequest"/>
                > > > > > <wsdl:output message="tns:DataServiceResponse"/>
                > > > > > </wsdl:operation>
                > > > > > </wsdl:portType>
                > > > > >
                > > > > > it will assume that the request message is empty, instead of
                > > > anyType.
                > > > > > However, I cannot create an element with type=xsd:anyType
                > since
                > > > the element
                > > > > > name will be appear under SOAPBody. Therefore, what should I
                > do?
                > > > > >
                > > > > > I would also like the wsdl to be ws-i complaince, is it
                > > > possible to do so?
                > > > > >
                > > > > > Cheers,
                > > > > > Sonna Nach
                > > > > >
                > > > > >
                > > > > > ________________________________
                > > > > > Yahoo! €?å·¥å?€?¦Â??- ?€?§ç½®?€
                > ?²æ­¢å½?€?Ã¥?€?¡ÂºÃ¨Â¦â?'³?€?Ã¥
                > €?ᴏ?€?½ï¼?> >
                > > > > >
                > > > > > -------------------------------------------------------------
                > ----
                > > > > > This group is a forum for the discussion of the WSDL
                > > > specification and its
                > > > > > implementation. Please stay on-topic.
                > > > > >
                > > > > >
                > > > > >
                > > > > > Yahoo! Groups Sponsor
                > > > > >
                > > > > > ADVERTISEMENT
                > > > > >
                > > > > >
                > > > > > ________________________________
                > > > > > Yahoo! Groups Links
                > > > > >
                > > > > >
                > > > > > To visit your group on the web, go to:
                > > > > > http://groups.yahoo.com/group/wsdl/
                > > > > >
                > > > > > To unsubscribe from this group, send an email to:
                > > > > > wsdl-unsubscribe@yahoogroups.com
                > > > > >
                > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                > > > Service.
                > > > > >
                > > > > >
                > > > > >
                > > >
                > > > -----------------------------------------------------------------
                > > > This group is a forum for the discussion of the WSDL
                > specification and its implementation. Please stay on-topic.
                > > > Yahoo! Groups Links
                > > >
                > > >
                > > >
                > > >
                > > >
                >
                > -----------------------------------------------------------------
                > This group is a forum for the discussion of the WSDL specification and its implementation. Please stay on-topic.
                > Yahoo! Groups Links
                >
                >
                >
                >
                >
              • Aleksander Slominski
                ... hmm, but if message content is xsd:any then anything is valid, right? maybe it would be possible to select schema to run based on QName of first child
                Message 7 of 9 , Mar 10, 2005
                  Anne Thomas Manes wrote:

                  >You can use any schema validator to validate the contents of the SOAP body.
                  >
                  >
                  hmm, but if message content is xsd:any then anything is valid, right?

                  maybe it would be possible to select schema to run based on QName of
                  first child inside DataServiceRequest?

                  sounds a bit like it may be stretching limits of static (XML schema
                  known and used to generate code) vs. dynamic validation (schema can be
                  added later).

                  did anybody do such dynamic schema selection/validation?

                  thanks,

                  alek
                  ps. is that WS-I compliant ;-)

                  >
                  >On Thu, 10 Mar 2005 06:04:28 -0000, question_simple
                  ><question_simple@...> wrote:
                  >
                  >
                  >>Thank you very much. Is there any tool which can check the validity
                  >>of soap message against the wsdl?
                  >>
                  >>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
                  >>
                  >>
                  >>>No -- it's impossible to make this scenario WS-I compliant. WS-I
                  >>>requires that the input message must provide a unique signature. The
                  >>>only way to make it WS-I compliant is to use a wrapper element.
                  >>>
                  >>><xsd:element name="tns:DataServiceRequest">
                  >>> <xsd:complexType>
                  >>> <xsd:sequence>
                  >>> <xsd:any/>
                  >>> </xsd:sequence>
                  >>> </xsd:complexType>
                  >>></xsd:element>
                  >>>
                  >>><wsdl:message name="DataServiceRequest">
                  >>> <wsdl:part element="tns:DataServiceRequest"
                  >>>
                  >>>
                  >>name="DataServiceRequest"/>
                  >>
                  >>
                  >>></wsdl:message>
                  >>>
                  >>>But this approach would produce messages like this:
                  >>>
                  >>><SOAP-ENV:Body>
                  >>> <tns:DataServiceRequest>
                  >>> <Tag1>It is ok</Tag1>
                  >>> </tns:DataServiceRequest>
                  >>></SOAP-ENV:Body>
                  >>>
                  >>>or
                  >>>
                  >>><SOAP-ENV:Body>
                  >>> <tns:DataServiceRequest>
                  >>> <Tag2>
                  >>> <Tag3>It is also ok</Tag3>
                  >>> </Tag2>
                  >>> </tns:DataServiceRequest>
                  >>></SOAP-ENV:Body>
                  >>>
                  >>>Anne
                  >>>
                  >>>On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
                  >>><question_simple@y...> wrote:
                  >>>
                  >>>
                  >>>>Hi,
                  >>>>
                  >>>> Thanks for your solution. However, it is not ws-i basic profile
                  >>>>
                  >>>>
                  >>1.1
                  >>
                  >>
                  >>>>compliance as it violates R2206 (http://www.ws-
                  >>>>i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
                  >>>>possible to make it ws-i compliance?
                  >>>>
                  >>>>Sonna Nach
                  >>>>
                  >>>>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
                  >>>>
                  >>>>
                  >>wrote:
                  >>
                  >>
                  >>>>>Try this:
                  >>>>>
                  >>>>><wsdl:message name="DataServiceRequest">
                  >>>>> <wsdl:part element="xsd:any" name="DataServiceRequest"/>
                  >>>>></wsdl:message>
                  >>>>>
                  >>>>>Anne
                  >>>>>
                  >>>>>
                  >>>>>On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
                  >>>>><question_simple@y...> wrote:
                  >>>>>
                  >>>>>
                  >>>>>>Hi All,
                  >>>>>>
                  >>>>>> I am writing a doc/lit web services, in which the elements
                  >>>>>>
                  >>>>>>
                  >>>>under SOAPBody
                  >>>>
                  >>>>
                  >>>>>>is unknown. That is, these two message are acceptable.
                  >>>>>>
                  >>>>>>1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
                  >>>>>>
                  >>>>>>2. <SOAP-ENV:Body><Tag2><Tag3>It is also
                  >>>>>>
                  >>>>>>
                  >>ok</Tag3></Tag2></SOAP-
                  >>
                  >>
                  >>>>ENV:Body>
                  >>>>
                  >>>>
                  >>>>>> The question is, if I write the wsdl as follows (pls refer
                  >>>>>>
                  >>>>>>
                  >>to
                  >>
                  >>
                  >>>>the attached
                  >>>>
                  >>>>
                  >>>>>>file)
                  >>>>>>
                  >>>>>><wsdl:message name="DataServiceRequest"/>
                  >>>>>> <wsdl:message name="DataServiceResponse">
                  >>>>>> <wsdl:part element="tns:DataServiceResponse"
                  >>>>>>name="DataServiceResponse"/>
                  >>>>>> </wsdl:message>
                  >>>>>>...
                  >>>>>>
                  >>>>>> <wsdl:portType name="DataServicePortType">
                  >>>>>> <wsdl:operation name="DataService">
                  >>>>>> <wsdl:input message="tns:DataServiceRequest"/>
                  >>>>>> <wsdl:output message="tns:DataServiceResponse"/>
                  >>>>>> </wsdl:operation>
                  >>>>>> </wsdl:portType>
                  >>>>>>
                  >>>>>> it will assume that the request message is empty, instead of
                  >>>>>>
                  >>>>>>
                  >>>>anyType.
                  >>>>
                  >>>>
                  >>>>>>However, I cannot create an element with type=xsd:anyType
                  >>>>>>
                  >>>>>>
                  >>since
                  >>
                  >>
                  >>>>the element
                  >>>>
                  >>>>
                  >>>>>>name will be appear under SOAPBody. Therefore, what should I
                  >>>>>>
                  >>>>>>
                  >>do?
                  >>
                  >>
                  >>>>>> I would also like the wsdl to be ws-i complaince, is it
                  >>>>>>
                  >>>>>>
                  >>>>possible to do so?
                  >>>>
                  >>>>
                  >>>>>>Cheers,
                  >>>>>>Sonna Nach
                  >>>>>>
                  >>>>>>
                  >>>>>>________________________________
                  >>>>>>Yahoo! €?å·¥å?€?¦Â??- ?€?§ç½®?€
                  >>>>>>
                  >>>>>>
                  >>?²æ­¢å½?€?Ã¥?€?¡ÂºÃ¨Â¦â?'³?€?Ã¥
                  >>€?ᴏ?€?½ï¼?> >
                  >>
                  >>
                  >>>>>> -------------------------------------------------------------
                  >>>>>>
                  >>>>>>
                  >>----
                  >>
                  >>
                  >>>>>> This group is a forum for the discussion of the WSDL
                  >>>>>>
                  >>>>>>
                  >>>>specification and its
                  >>>>
                  >>>>
                  >>>>>>implementation. Please stay on-topic.
                  >>>>>>
                  >>>>>>
                  >>>>>>
                  >>>>>> Yahoo! Groups Sponsor
                  >>>>>>
                  >>>>>> ADVERTISEMENT
                  >>>>>>
                  >>>>>>
                  >>>>>> ________________________________
                  >>>>>> Yahoo! Groups Links
                  >>>>>>
                  >>>>>>
                  >>>>>>To visit your group on the web, go to:
                  >>>>>>http://groups.yahoo.com/group/wsdl/
                  >>>>>>
                  >>>>>>To unsubscribe from this group, send an email to:
                  >>>>>>wsdl-unsubscribe@yahoogroups.com
                  >>>>>>
                  >>>>>>Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                  >>>>>>
                  >>>>>>
                  >>>>Service.
                  >>>>
                  >>>>
                  >>>>>>
                  >>>>>>
                  >>>>>>
                  >>>>-----------------------------------------------------------------
                  >>>>This group is a forum for the discussion of the WSDL
                  >>>>
                  >>>>
                  >>specification and its implementation. Please stay on-topic.
                  >>
                  >>
                  >>>>Yahoo! Groups Links
                  >>>>
                  >>>>
                  >>>>
                  >>>>
                  >>>>
                  >>>>
                  >>>>
                  >>-----------------------------------------------------------------
                  >>This group is a forum for the discussion of the WSDL specification and its implementation. Please stay on-topic.
                  >>Yahoo! Groups Links
                  >>
                  >>
                  >>
                  >>
                  >>
                  >>
                  >>
                  >
                  >
                  >-----------------------------------------------------------------
                  >This group is a forum for the discussion of the WSDL specification and its implementation. Please stay on-topic.
                  >Yahoo! Groups Links
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >


                  --
                  The best way to predict the future is to invent it - Alan Kay
                • Vivek krishna
                  Dynamic validation wouldnt be necessary if the wsdl author mentioned which namespace the elements under belong to . XML schema provides a way to
                  Message 8 of 9 , Mar 10, 2005
                    Dynamic validation wouldnt be necessary if the wsdl author mentioned
                    which namespace the elements under <xsd:any> belong to .
                    XML schema provides a way to attach a namespace to xsd:any
                    <xsd:any namespace="some namespace" />

                    Vivek
                    --- In wsdl@yahoogroups.com, Aleksander Slominski <aslom@c...> wrote:
                    > Anne Thomas Manes wrote:
                    >
                    > >You can use any schema validator to validate the contents of the
                    SOAP body.
                    > >
                    > >
                    > hmm, but if message content is xsd:any then anything is valid, right?
                    >
                    > maybe it would be possible to select schema to run based on QName of
                    > first child inside DataServiceRequest?
                    >
                    > sounds a bit like it may be stretching limits of static (XML schema
                    > known and used to generate code) vs. dynamic validation (schema can be
                    > added later).
                    >
                    > did anybody do such dynamic schema selection/validation?
                    >
                    > thanks,
                    >
                    > alek
                    > ps. is that WS-I compliant ;-)
                    >
                    > >
                    > >On Thu, 10 Mar 2005 06:04:28 -0000, question_simple
                    > ><question_simple@y...> wrote:
                    > >
                    > >
                    > >>Thank you very much. Is there any tool which can check the validity
                    > >>of soap message against the wsdl?
                    > >>
                    > >>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
                    > >>
                    > >>
                    > >>>No -- it's impossible to make this scenario WS-I compliant. WS-I
                    > >>>requires that the input message must provide a unique signature. The
                    > >>>only way to make it WS-I compliant is to use a wrapper element.
                    > >>>
                    > >>><xsd:element name="tns:DataServiceRequest">
                    > >>> <xsd:complexType>
                    > >>> <xsd:sequence>
                    > >>> <xsd:any/>
                    > >>> </xsd:sequence>
                    > >>> </xsd:complexType>
                    > >>></xsd:element>
                    > >>>
                    > >>><wsdl:message name="DataServiceRequest">
                    > >>> <wsdl:part element="tns:DataServiceRequest"
                    > >>>
                    > >>>
                    > >>name="DataServiceRequest"/>
                    > >>
                    > >>
                    > >>></wsdl:message>
                    > >>>
                    > >>>But this approach would produce messages like this:
                    > >>>
                    > >>><SOAP-ENV:Body>
                    > >>> <tns:DataServiceRequest>
                    > >>> <Tag1>It is ok</Tag1>
                    > >>> </tns:DataServiceRequest>
                    > >>></SOAP-ENV:Body>
                    > >>>
                    > >>>or
                    > >>>
                    > >>><SOAP-ENV:Body>
                    > >>> <tns:DataServiceRequest>
                    > >>> <Tag2>
                    > >>> <Tag3>It is also ok</Tag3>
                    > >>> </Tag2>
                    > >>> </tns:DataServiceRequest>
                    > >>></SOAP-ENV:Body>
                    > >>>
                    > >>>Anne
                    > >>>
                    > >>>On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
                    > >>><question_simple@y...> wrote:
                    > >>>
                    > >>>
                    > >>>>Hi,
                    > >>>>
                    > >>>> Thanks for your solution. However, it is not ws-i basic profile
                    > >>>>
                    > >>>>
                    > >>1.1
                    > >>
                    > >>
                    > >>>>compliance as it violates R2206 (http://www.ws-
                    > >>>>i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
                    > >>>>possible to make it ws-i compliance?
                    > >>>>
                    > >>>>Sonna Nach
                    > >>>>
                    > >>>>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
                    > >>>>
                    > >>>>
                    > >>wrote:
                    > >>
                    > >>
                    > >>>>>Try this:
                    > >>>>>
                    > >>>>><wsdl:message name="DataServiceRequest">
                    > >>>>> <wsdl:part element="xsd:any" name="DataServiceRequest"/>
                    > >>>>></wsdl:message>
                    > >>>>>
                    > >>>>>Anne
                    > >>>>>
                    > >>>>>
                    > >>>>>On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
                    > >>>>><question_simple@y...> wrote:
                    > >>>>>
                    > >>>>>
                    > >>>>>>Hi All,
                    > >>>>>>
                    > >>>>>> I am writing a doc/lit web services, in which the elements
                    > >>>>>>
                    > >>>>>>
                    > >>>>under SOAPBody
                    > >>>>
                    > >>>>
                    > >>>>>>is unknown. That is, these two message are acceptable.
                    > >>>>>>
                    > >>>>>>1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
                    > >>>>>>
                    > >>>>>>2. <SOAP-ENV:Body><Tag2><Tag3>It is also
                    > >>>>>>
                    > >>>>>>
                    > >>ok</Tag3></Tag2></SOAP-
                    > >>
                    > >>
                    > >>>>ENV:Body>
                    > >>>>
                    > >>>>
                    > >>>>>> The question is, if I write the wsdl as follows (pls refer
                    > >>>>>>
                    > >>>>>>
                    > >>to
                    > >>
                    > >>
                    > >>>>the attached
                    > >>>>
                    > >>>>
                    > >>>>>>file)
                    > >>>>>>
                    > >>>>>><wsdl:message name="DataServiceRequest"/>
                    > >>>>>> <wsdl:message name="DataServiceResponse">
                    > >>>>>> <wsdl:part element="tns:DataServiceResponse"
                    > >>>>>>name="DataServiceResponse"/>
                    > >>>>>> </wsdl:message>
                    > >>>>>>...
                    > >>>>>>
                    > >>>>>> <wsdl:portType name="DataServicePortType">
                    > >>>>>> <wsdl:operation name="DataService">
                    > >>>>>> <wsdl:input message="tns:DataServiceRequest"/>
                    > >>>>>> <wsdl:output message="tns:DataServiceResponse"/>
                    > >>>>>> </wsdl:operation>
                    > >>>>>> </wsdl:portType>
                    > >>>>>>
                    > >>>>>> it will assume that the request message is empty, instead of
                    > >>>>>>
                    > >>>>>>
                    > >>>>anyType.
                    > >>>>
                    > >>>>
                    > >>>>>>However, I cannot create an element with type=xsd:anyType
                    > >>>>>>
                    > >>>>>>
                    > >>since
                    > >>
                    > >>
                    > >>>>the element
                    > >>>>
                    > >>>>
                    > >>>>>>name will be appear under SOAPBody. Therefore, what should I
                    > >>>>>>
                    > >>>>>>
                    > >>do?
                    > >>
                    > >>
                    > >>>>>> I would also like the wsdl to be ws-i complaince, is it
                    > >>>>>>
                    > >>>>>>
                    > >>>>possible to do so?
                    > >>>>
                    > >>>>
                    > >>>>>>Cheers,
                    > >>>>>>Sonna Nach
                    > >>>>>>
                    > >>>>>>
                    > >>>>>>________________________________
                    > >>>>>>Yahoo! €?å·¥å?€?¦Â??- ?€?§ç½®?€
                    > >>>>>>
                    > >>>>>>
                    > >>?²æ­¢å½?€?Ã¥?€?¡ÂºÃ¨Â¦â?'³?€?Ã¥
                    > >>€?ᴏ?€?½ï¼?> >
                    > >>
                    > >>
                    > >>>>>> -------------------------------------------------------------
                    > >>>>>>
                    > >>>>>>
                    > >>----
                    > >>
                    > >>
                    > >>>>>> This group is a forum for the discussion of the WSDL
                    > >>>>>>
                    > >>>>>>
                    > >>>>specification and its
                    > >>>>
                    > >>>>
                    > >>>>>>implementation. Please stay on-topic.
                    > >>>>>>
                    > >>>>>>
                    > >>>>>>
                    > >>>>>> Yahoo! Groups Sponsor
                    > >>>>>>
                    > >>>>>> ADVERTISEMENT
                    > >>>>>>
                    > >>>>>>
                    > >>>>>> ________________________________
                    > >>>>>> Yahoo! Groups Links
                    > >>>>>>
                    > >>>>>>
                    > >>>>>>To visit your group on the web, go to:
                    > >>>>>>http://groups.yahoo.com/group/wsdl/
                    > >>>>>>
                    > >>>>>>To unsubscribe from this group, send an email to:
                    > >>>>>>wsdl-unsubscribe@yahoogroups.com
                    > >>>>>>
                    > >>>>>>Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                    > >>>>>>
                    > >>>>>>
                    > >>>>Service.
                    > >>>>
                    > >>>>
                    > >>>>>>
                    > >>>>>>
                    > >>>>>>
                    > >>>>-----------------------------------------------------------------
                    > >>>>This group is a forum for the discussion of the WSDL
                    > >>>>
                    > >>>>
                    > >>specification and its implementation. Please stay on-topic.
                    > >>
                    > >>
                    > >>>>Yahoo! Groups Links
                    > >>>>
                    > >>>>
                    > >>>>
                    > >>>>
                    > >>>>
                    > >>>>
                    > >>>>
                    > >>-----------------------------------------------------------------
                    > >>This group is a forum for the discussion of the WSDL specification
                    and its implementation. Please stay on-topic.
                    > >>Yahoo! Groups Links
                    > >>
                    > >>
                    > >>
                    > >>
                    > >>
                    > >>
                    > >>
                    > >
                    > >
                    > >-----------------------------------------------------------------
                    > >This group is a forum for the discussion of the WSDL specification
                    and its implementation. Please stay on-topic.
                    > >Yahoo! Groups Links
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >
                    >
                    >
                    > --
                    > The best way to predict the future is to invent it - Alan Kay
                  • Anne Thomas Manes
                    A namespace URI doesn t always point to a schema. But you could pass a schema location or an inline schema with the message. Anne
                    Message 9 of 9 , Mar 11, 2005
                      A namespace URI doesn't always point to a schema. But you could pass a
                      schema location or an inline schema with the message.

                      Anne


                      On Fri, 11 Mar 2005 06:07:38 -0000, Vivek krishna <vivekk@...> wrote:
                      >
                      >
                      > Dynamic validation wouldnt be necessary if the wsdl author mentioned
                      > which namespace the elements under <xsd:any> belong to .
                      > XML schema provides a way to attach a namespace to xsd:any
                      > <xsd:any namespace="some namespace" />
                      >
                      > Vivek
                      > --- In wsdl@yahoogroups.com, Aleksander Slominski <aslom@c...> wrote:
                      > > Anne Thomas Manes wrote:
                      > >
                      > > >You can use any schema validator to validate the contents of the
                      > SOAP body.
                      > > >
                      > > >
                      > > hmm, but if message content is xsd:any then anything is valid, right?
                      > >
                      > > maybe it would be possible to select schema to run based on QName of
                      > > first child inside DataServiceRequest?
                      > >
                      > > sounds a bit like it may be stretching limits of static (XML schema
                      > > known and used to generate code) vs. dynamic validation (schema can be
                      > > added later).
                      > >
                      > > did anybody do such dynamic schema selection/validation?
                      > >
                      > > thanks,
                      > >
                      > > alek
                      > > ps. is that WS-I compliant ;-)
                      > >
                      > > >
                      > > >On Thu, 10 Mar 2005 06:04:28 -0000, question_simple
                      > > ><question_simple@y...> wrote:
                      > > >
                      > > >
                      > > >>Thank you very much. Is there any tool which can check the validity
                      > > >>of soap message against the wsdl?
                      > > >>
                      > > >>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...> wrote:
                      > > >>
                      > > >>
                      > > >>>No -- it's impossible to make this scenario WS-I compliant. WS-I
                      > > >>>requires that the input message must provide a unique signature. The
                      > > >>>only way to make it WS-I compliant is to use a wrapper element.
                      > > >>>
                      > > >>><xsd:element name="tns:DataServiceRequest">
                      > > >>> <xsd:complexType>
                      > > >>> <xsd:sequence>
                      > > >>> <xsd:any/>
                      > > >>> </xsd:sequence>
                      > > >>> </xsd:complexType>
                      > > >>></xsd:element>
                      > > >>>
                      > > >>><wsdl:message name="DataServiceRequest">
                      > > >>> <wsdl:part element="tns:DataServiceRequest"
                      > > >>>
                      > > >>>
                      > > >>name="DataServiceRequest"/>
                      > > >>
                      > > >>
                      > > >>></wsdl:message>
                      > > >>>
                      > > >>>But this approach would produce messages like this:
                      > > >>>
                      > > >>><SOAP-ENV:Body>
                      > > >>> <tns:DataServiceRequest>
                      > > >>> <Tag1>It is ok</Tag1>
                      > > >>> </tns:DataServiceRequest>
                      > > >>></SOAP-ENV:Body>
                      > > >>>
                      > > >>>or
                      > > >>>
                      > > >>><SOAP-ENV:Body>
                      > > >>> <tns:DataServiceRequest>
                      > > >>> <Tag2>
                      > > >>> <Tag3>It is also ok</Tag3>
                      > > >>> </Tag2>
                      > > >>> </tns:DataServiceRequest>
                      > > >>></SOAP-ENV:Body>
                      > > >>>
                      > > >>>Anne
                      > > >>>
                      > > >>>On Wed, 09 Mar 2005 07:47:20 -0000, question_simple
                      > > >>><question_simple@y...> wrote:
                      > > >>>
                      > > >>>
                      > > >>>>Hi,
                      > > >>>>
                      > > >>>> Thanks for your solution. However, it is not ws-i basic profile
                      > > >>>>
                      > > >>>>
                      > > >>1.1
                      > > >>
                      > > >>
                      > > >>>>compliance as it violates R2206 (http://www.ws-
                      > > >>>>i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.htm#R2206). Is it
                      > > >>>>possible to make it ws-i compliance?
                      > > >>>>
                      > > >>>>Sonna Nach
                      > > >>>>
                      > > >>>>--- In wsdl@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
                      > > >>>>
                      > > >>>>
                      > > >>wrote:
                      > > >>
                      > > >>
                      > > >>>>>Try this:
                      > > >>>>>
                      > > >>>>><wsdl:message name="DataServiceRequest">
                      > > >>>>> <wsdl:part element="xsd:any" name="DataServiceRequest"/>
                      > > >>>>></wsdl:message>
                      > > >>>>>
                      > > >>>>>Anne
                      > > >>>>>
                      > > >>>>>
                      > > >>>>>On Tue, 8 Mar 2005 11:24:25 +0800 (CST), Question Simple
                      > > >>>>><question_simple@y...> wrote:
                      > > >>>>>
                      > > >>>>>
                      > > >>>>>>Hi All,
                      > > >>>>>>
                      > > >>>>>> I am writing a doc/lit web services, in which the elements
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>under SOAPBody
                      > > >>>>
                      > > >>>>
                      > > >>>>>>is unknown. That is, these two message are acceptable.
                      > > >>>>>>
                      > > >>>>>>1. <SOAP-ENV:Body><Tag1>It is ok</Tag1></SOAP-ENV:Body>
                      > > >>>>>>
                      > > >>>>>>2. <SOAP-ENV:Body><Tag2><Tag3>It is also
                      > > >>>>>>
                      > > >>>>>>
                      > > >>ok</Tag3></Tag2></SOAP-
                      > > >>
                      > > >>
                      > > >>>>ENV:Body>
                      > > >>>>
                      > > >>>>
                      > > >>>>>> The question is, if I write the wsdl as follows (pls refer
                      > > >>>>>>
                      > > >>>>>>
                      > > >>to
                      > > >>
                      > > >>
                      > > >>>>the attached
                      > > >>>>
                      > > >>>>
                      > > >>>>>>file)
                      > > >>>>>>
                      > > >>>>>><wsdl:message name="DataServiceRequest"/>
                      > > >>>>>> <wsdl:message name="DataServiceResponse">
                      > > >>>>>> <wsdl:part element="tns:DataServiceResponse"
                      > > >>>>>>name="DataServiceResponse"/>
                      > > >>>>>> </wsdl:message>
                      > > >>>>>>...
                      > > >>>>>>
                      > > >>>>>> <wsdl:portType name="DataServicePortType">
                      > > >>>>>> <wsdl:operation name="DataService">
                      > > >>>>>> <wsdl:input message="tns:DataServiceRequest"/>
                      > > >>>>>> <wsdl:output message="tns:DataServiceResponse"/>
                      > > >>>>>> </wsdl:operation>
                      > > >>>>>> </wsdl:portType>
                      > > >>>>>>
                      > > >>>>>> it will assume that the request message is empty, instead of
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>anyType.
                      > > >>>>
                      > > >>>>
                      > > >>>>>>However, I cannot create an element with type=xsd:anyType
                      > > >>>>>>
                      > > >>>>>>
                      > > >>since
                      > > >>
                      > > >>
                      > > >>>>the element
                      > > >>>>
                      > > >>>>
                      > > >>>>>>name will be appear under SOAPBody. Therefore, what should I
                      > > >>>>>>
                      > > >>>>>>
                      > > >>do?
                      > > >>
                      > > >>
                      > > >>>>>> I would also like the wsdl to be ws-i complaince, is it
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>possible to do so?
                      > > >>>>
                      > > >>>>
                      > > >>>>>>Cheers,
                      > > >>>>>>Sonna Nach
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>>________________________________
                      > > >>>>>>Yahoo! €?å·¥å?€?¦Â??- ?€?§ç½®?€
                      > > >>>>>>
                      > > >>>>>>
                      > > >>?²æ­¢å½?€?Ã¥?€?¡ÂºÃ¨Â¦â?'³?€?Ã¥
                      > > >>€?ᴏ?€?½ï¼?> >
                      > > >>
                      > > >>
                      > > >>>>>> -------------------------------------------------------------
                      > > >>>>>>
                      > > >>>>>>
                      > > >>----
                      > > >>
                      > > >>
                      > > >>>>>> This group is a forum for the discussion of the WSDL
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>specification and its
                      > > >>>>
                      > > >>>>
                      > > >>>>>>implementation. Please stay on-topic.
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>> Yahoo! Groups Sponsor
                      > > >>>>>>
                      > > >>>>>> ADVERTISEMENT
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>> ________________________________
                      > > >>>>>> Yahoo! Groups Links
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>>To visit your group on the web, go to:
                      > > >>>>>>http://groups.yahoo.com/group/wsdl/
                      > > >>>>>>
                      > > >>>>>>To unsubscribe from this group, send an email to:
                      > > >>>>>>wsdl-unsubscribe@yahoogroups.com
                      > > >>>>>>
                      > > >>>>>>Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>Service.
                      > > >>>>
                      > > >>>>
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>>>
                      > > >>>>-----------------------------------------------------------------
                      > > >>>>This group is a forum for the discussion of the WSDL
                      > > >>>>
                      > > >>>>
                      > > >>specification and its implementation. Please stay on-topic.
                      > > >>
                      > > >>
                      > > >>>>Yahoo! Groups Links
                      > > >>>>
                      > > >>>>
                      > > >>>>
                      > > >>>>
                      > > >>>>
                      > > >>>>
                      > > >>>>
                      > > >>-----------------------------------------------------------------
                      > > >>This group is a forum for the discussion of the WSDL specification
                      > and its implementation. Please stay on-topic.
                      > > >>Yahoo! Groups Links
                      > > >>
                      > > >>
                      > > >>
                      > > >>
                      > > >>
                      > > >>
                      > > >>
                      > > >
                      > > >
                      > > >-----------------------------------------------------------------
                      > > >This group is a forum for the discussion of the WSDL specification
                      > and its implementation. Please stay on-topic.
                      > > >Yahoo! Groups Links
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > > >
                      > >
                      > >
                      > > --
                      > > The best way to predict the future is to invent it - Alan Kay
                      >
                      > -----------------------------------------------------------------
                      > This group is a forum for the discussion of the WSDL specification and its implementation. Please stay on-topic.
                      > Yahoo! Groups Links
                      >
                      >
                      >
                      >
                      >
                    Your message has been successfully submitted and would be delivered to recipients shortly.