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

Re: [soapbuilders] Round 4 "Fault" test endpoint

Expand Messages
  • Arun Gupta
    Athough that s a good approach, but I ve defined the test spec such that either a fault is the only fault thrown from the method or if it s thrown along with
    Message 1 of 24 , Sep 5, 2002
    • 0 Attachment
      Athough that's a good approach, but I've defined the test spec such that
      either a fault is the only fault thrown from the method or if it's
      thrown along with other faults, it's thrown for the same parameter value
      in different methods. This makes the programming little easier where you
      may define variables at the top level and use them across different
      method invocations.

      Also, the fault codes in all your responses in env:Client instead of
      env:Server. Can you please check that ?

      Thanks,
      -Arun

      Bob Cunnings wrote:

      > Hi,
      >
      > Ok, I see the problem. I naively associated the fault message with an input
      > parameter value based on the name of the fault message (e.g. SimpleFault1 to
      > "1", but it really maps to "2"), which fails for that operation.
      >
      > The same goes for the others. I'll get this fixed later today. Yes, it's
      > important to adhere to the spec!
      >
      > RC
      >
      >
      > > Hi Bob,
      > >
      > > I ran JAX-RPC clients against your "fault" endpoint.
      > >
      > > In simple-rpc-encoded, if you can change your service implementation to
      > > throw faults as per the test specification at
      > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html then
      > > echoMultipleFaults2 will throw StringFault and FloatFault in the correct
      > > order. Other than that all tests pass.
      > >
      > > Similarly some of the exceptions thrown in complex-rpc-encoded are also
      > > not as per the test specification.
      > >
      > > I know I posted the specification yesterday only, but it's important
      > > that we stick to that since that is the basis for us to ensure correct
      > > faults are thrown by the server and expected by the client accordingly.
      > >
      > > Regards,
      > > -Arun
      > >
      > >
      >
      >
      >
      >
      >
      > Yahoo! Groups Sponsor
      > ADVERTISEMENT
      > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=0/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
      > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=1/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
      >
      >
      >
      > -----------------------------------------------------------------
      > This group is a forum for builders of SOAP implementations to discuss
      > implementation and interoperability issues. Please stay on-topic.
      >
      > To unsubscribe from this group, send an email to:
      > soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >
      > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
      > <http://docs.yahoo.com/info/terms/>.


      --
      =============================================
      There is only one me, I must live myself!
      There is only one today, I must live itself!
      =============================================
      http://members.tripod.com/~apgupta/index.html
      =============================================
    • Arun Gupta
      I ll update the test specification to mention that env:Server is the expected fault code in all the faults. It s a good idea to define a new fault message. But
      Message 2 of 24 , Sep 5, 2002
      • 0 Attachment
        I'll update the test specification to mention that env:Server is the
        expected fault code in all the faults.

        It's a good idea to define a new fault message. But can we construct
        this fault such that this also tests another aspect of fault interop.
        Another option we can change the test spec such that:

        Throws empty fault when the parameter = 1 or not 2 or not 3.
        Throws fault with a xsd:string member when the parameter = 2.
        Throws fault with a xsd:float[] member when the parameter = 3.

        Thus there is a default behavior for each method and there is out of
        range input parameter. Let me know which one you prefer ?

        Regards,
        -Arun

        Bob Cunnings wrote:

        > Hi,
        >
        > Which fault code do you want? The spec is silent on that point, but
        > I can see the case for the presumption that it's the server that's at
        > fault. It's no problem to change it.
        >
        > What is the expected behavior when an input parameter is out of
        > range?
        >
        > It might make sense to specify that env:Server is used except in
        > when an improper request is received, e.g. an input parameter is
        > out of range. Then env:client would be required. A fault message
        > might even be defined for use in such a case, perhaps echoing the
        > invalid param value, or whatever. Just a thought.
        >
        > Thanks,
        >
        > RC
        >
        > > Athough that's a good approach, but I've defined the test spec such
        > that
        > > either a fault is the only fault thrown from the method or if it's
        > > thrown along with other faults, it's thrown for the same parameter
        > value
        > > in different methods. This makes the programming little easier where
        > you
        > > may define variables at the top level and use them across different
        > > method invocations.
        > >
        > > Also, the fault codes in all your responses in env:Client instead of
        > > env:Server. Can you please check that ?
        > >
        > > Thanks,
        > > -Arun
        > >
        > > Bob Cunnings wrote:
        > >
        > > > Hi,
        > > >
        > > > Ok, I see the problem. I naively associated the fault message with
        > an input
        > > > parameter value based on the name of the fault message (e.g.
        > SimpleFault1 to
        > > > "1", but it really maps to "2"), which fails for that operation.
        > > >
        > > > The same goes for the others. I'll get this fixed later today.
        > Yes, it's
        > > > important to adhere to the spec!
        > > >
        > > > RC
        > > >
        > > >
        > > > > Hi Bob,
        > > > >
        > > > > I ran JAX-RPC clients against your "fault" endpoint.
        > > > >
        > > > > In simple-rpc-encoded, if you can change your service
        > implementation to
        > > > > throw faults as per the test specification at
        > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html then
        > > > > echoMultipleFaults2 will throw StringFault and FloatFault in
        > the correct
        > > > > order. Other than that all tests pass.
        > > > >
        > > > > Similarly some of the exceptions thrown in complex-rpc-encoded
        > are also
        > > > > not as per the test specification.
        > > > >
        > > > > I know I posted the specification yesterday only, but it's
        > important
        > > > > that we stick to that since that is the basis for us to ensure
        > correct
        > > > > faults are thrown by the server and expected by the client
        > accordingly.
        > > > >
        > > > > Regards,
        > > > > -Arun
        > > > >
        > > > >
        > > >
        > > >
        > > >
        > > >
        > > >
        > > > Yahoo! Groups Sponsor
        > > > ADVERTISEMENT
        > > > <
        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=0/
        >
        > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
        > > > <
        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=1/
        >
        > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
        > > >
        > > >
        > > >
        > > > -----------------------------------------------------------------
        > > > This group is a forum for builders of SOAP implementations to discuss
        > > > implementation and interoperability issues. Please stay on-topic.
        > > >
        > > > To unsubscribe from this group, send an email to:
        > > > soapbuilders-unsubscribe@yahoogroups.com
        > > >
        > > >
        > > >
        > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
        > > > <http://docs.yahoo.com/info/terms/ >.
        > >
        > >
        > > --
        > > =============================================
        > > There is only one me, I must live myself!
        > > There is only one today, I must live itself!
        > > =============================================
        > > http://members.tripod.com/~apgupta/index.html
        > <http://members.tripod.com/%7Eapgupta/index.html>
        > > =============================================
        > >
        > >
        > >
        > >
        > > -----------------------------------------------------------------
        > > This group is a forum for builders of SOAP implementations to
        > discuss implementation and interope
        > rability issues. Please stay on-topic.
        > >
        > > To unsubscribe from this group, send an email to:
        > > soapbuilders-unsubscribe@yahoogroups.com
        > >
        > >
        > >
        > > Your use of Yahoo! Groups is subject to
        > http://docs.yahoo.com/info/terms/
        > >
        >
        >
        >
        > Yahoo! Groups Sponsor
        > ADVERTISEMENT
        > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
        >
        >
        >
        > -----------------------------------------------------------------
        > This group is a forum for builders of SOAP implementations to discuss
        > implementation and interoperability issues. Please stay on-topic.
        >
        > To unsubscribe from this group, send an email to:
        > soapbuilders-unsubscribe@yahoogroups.com
        >
        >
        >
        > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
        > <http://docs.yahoo.com/info/terms/> .


        --
        =============================================
        There is only one me, I must live myself!
        There is only one today, I must live itself!
        =============================================
        http://members.tripod.com/~apgupta/index.html
        =============================================
      • Arun Gupta
        Sure. You can find the fault interop test specs at http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Bob is maintaining the entire set of round 4
        Message 3 of 24 , Sep 5, 2002
        • 0 Attachment
          Sure.

          You can find the fault interop test specs at
          http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Bob is
          maintaining the entire set of round 4 specifications at
          http://www.whitemesa.net/r4/interop4.html.

          Regards,
          -Arun

          Kingsley Idehen wrote:

          > All,
          >
          >
          >
          > Is there a URL for the round 4 test specs?
          >
          >
          >
          > Kingsley Idehen
          >
          > OpenLink Software
          >
          >
          >
          > -----Original Message-----
          > From: Arun Gupta [mailto:arun.gupta@...]
          > Sent: Thursday, September 05, 2002 1:26 PM
          > To: soapbuilders@yahoogroups.com
          > Subject: Re: [soapbuilders] Round 4 "Fault" test endpoint
          >
          >
          >
          > I'll update the test specification to mention that env:Server is the
          > expected fault code in all the faults.
          >
          > It's a good idea to define a new fault message. But can we construct
          > this fault such that this also tests another aspect of fault interop.
          > Another option we can change the test spec such that:
          >
          > Throws empty fault when the parameter = 1 or not 2 or not 3.
          > Throws fault with a xsd:string member when the parameter = 2.
          > Throws fault with a xsd:float[] member when the parameter = 3.
          >
          > Thus there is a default behavior for each method and there is out of
          > range input parameter. Let me know which one you prefer ?
          >
          > Regards,
          > -Arun
          >
          > Bob Cunnings wrote:
          >
          > > Hi,
          > >
          > > Which fault code do you want? The spec is silent on that point, but
          > > I can see the case for the presumption that it's the server that's at
          > > fault. It's no problem to change it.
          > >
          > > What is the expected behavior when an input parameter is out of
          > > range?
          > >
          > > It might make sense to specify that env:Server is used except in
          > > when an improper request is received, e.g. an input parameter is
          > > out of range. Then env:client would be required. A fault message
          > > might even be defined for use in such a case, perhaps echoing the
          > > invalid param value, or whatever. Just a thought.
          > >
          > > Thanks,
          > >
          > > RC
          > >
          > > > Athough that's a good approach, but I've defined the test spec such
          > > that
          > > > either a fault is the only fault thrown from the method or if it's
          > > > thrown along with other faults, it's thrown for the same parameter
          > > value
          > > > in different methods. This makes the programming little easier where
          > > you
          > > > may define variables at the top level and use them across different
          > > > method invocations.
          > > >
          > > > Also, the fault codes in all your responses in env:Client instead of
          > > > env:Server. Can you please check that ?
          > > >
          > > > Thanks,
          > > > -Arun
          > > >
          > > > Bob Cunnings wrote:
          > > >
          > > > > Hi,
          > > > >
          > > > > Ok, I see the problem. I naively associated the fault message with
          > > an input
          > > > > parameter value based on the name of the fault message (e.g.
          > > SimpleFault1 to
          > > > > "1", but it really maps to "2"), which fails for that operation.
          > > > >
          > > > > The same goes for the others. I'll get this fixed later today.
          > > Yes, it's
          > > > > important to adhere to the spec!
          > > > >
          > > > > RC
          > > > >
          > > > >
          > > > > > Hi Bob,
          > > > > >
          > > > > > I ran JAX-RPC clients against your "fault" endpoint.
          > > > > >
          > > > > > In simple-rpc-encoded, if you can change your service
          > > implementation to
          > > > > > throw faults as per the test specification at
          > > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html then
          > > > > > echoMultipleFaults2 will throw StringFault and FloatFault in
          > > the correct
          > > > > > order. Other than that all tests pass.
          > > > > >
          > > > > > Similarly some of the exceptions thrown in complex-rpc-encoded
          > > are also
          > > > > > not as per the test specification.
          > > > > >
          > > > > > I know I posted the specification yesterday only, but it's
          > > important
          > > > > > that we stick to that since that is the basis for us to ensure
          > > correct
          > > > > > faults are thrown by the server and expected by the client
          > > accordingly.
          > > > > >
          > > > > > Regards,
          > > > > > -Arun
          > > > > >
          > > > > >
          > > > >
          > > > >
          > > > >
          > > > >
          > > > >
          > > > > Yahoo! Groups Sponsor
          > > > > ADVERTISEMENT
          > > > > <
          > >
          > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=0/
          >
          > >
          > > * http://geocities.yahoo.com/ps/info?.refer=blrecs >
          > > > > <
          > >
          > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=1/
          >
          > >
          > > * http://geocities.yahoo.com/ps/info?.refer=blrecs >
          > > > >
          > > > >
          > > > >
          > > > > -----------------------------------------------------------------
          > > > > This group is a forum for builders of SOAP implementations to
          > discuss
          > > > > implementation and interoperability issues. Please stay on-topic.
          > > > >
          > > > > To unsubscribe from this group, send an email to:
          > > > > soapbuilders-unsubscribe@yahoogroups.com
          > > > >
          > > > >
          > > > >
          > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
          > > > > < http://docs.yahoo.com/info/terms/ >.
          > > >
          > > >
          > > > --
          > > > =============================================
          > > > There is only one me, I must live myself!
          > > > There is only one today, I must live itself!
          > > > =============================================
          > > > http://members.tripod.com/~apgupta/index.html
          > <http://members.tripod.com/%7Eapgupta/index.html>
          > > < http://members.tripod.com/%7Eapgupta/index.html >
          > > > =============================================
          > > >
          > > >
          > > >
          > > >
          > > > -----------------------------------------------------------------
          > > > This group is a forum for builders of SOAP implementations to
          > > discuss implementation and interope
          > > rability issues. Please stay on-topic.
          > > >
          > > > To unsubscribe from this group, send an email to:
          > > > soapbuilders-unsubscribe@yahoogroups.com
          > > >
          > > >
          > > >
          > > > Your use of Yahoo! Groups is subject to
          > > http://docs.yahoo.com/info/terms/
          > > >
          > >
          > >
          > >
          > > Yahoo! Groups Sponsor
          > > ADVERTISEMENT
          > > <
          > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/
          > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http:/www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
          > >
          > >
          > >
          > >
          > > -----------------------------------------------------------------
          > > This group is a forum for builders of SOAP implementations to discuss
          > > implementation and interoperability issues. Please stay on-topic.
          > >
          > > To unsubscribe from this group, send an email to:
          > > soapbuilders-unsubscribe@yahoogroups.com
          > >
          > >
          > >
          > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
          > > < http://docs.yahoo.com/info/terms/ > .
          >
          >
          > --
          > =============================================
          > There is only one me, I must live myself!
          > There is only one today, I must live itself!
          > =============================================
          > http://members.tripod.com/~apgupta/index.html
          > <http://members.tripod.com/%7Eapgupta/index.html>
          > =============================================
          >
          >
          >
          >
          > -----------------------------------------------------------------
          > This group is a forum for builders of SOAP implementations to discuss
          > implementation and interoperability issues. Please stay on-topic.
          >
          > To unsubscribe from this group, send an email to:
          > soapbuilders-unsubscribe@yahoogroups.com
          >
          >
          >
          > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
          > <http://docs.yahoo.com/info/terms/> .
          >
          >
          >
          > Yahoo! Groups Sponsor
          > ADVERTISEMENT
          > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
          >
          >
          >
          > -----------------------------------------------------------------
          > This group is a forum for builders of SOAP implementations to discuss
          > implementation and interoperability issues. Please stay on-topic.
          >
          > To unsubscribe from this group, send an email to:
          > soapbuilders-unsubscribe@yahoogroups.com
          >
          >
          >
          > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
          > <http://docs.yahoo.com/info/terms/> .


          --
          =============================================
          There is only one me, I must live myself!
          There is only one today, I must live itself!
          =============================================
          http://members.tripod.com/~apgupta/index.html
          =============================================
        • Kingsley Idehen
          All, Is there a URL for the round 4 test specs? Kingsley Idehen OpenLink Software ... From: Arun Gupta [mailto:arun.gupta@sun.com] Sent: Thursday, September
          Message 4 of 24 , Sep 5, 2002
          • 0 Attachment

            All,

             

            Is there a URL for the round 4 test specs?

             

            Kingsley Idehen

            OpenLink Software

             

            -----Original Message-----
            From: Arun Gupta [mailto:arun.gupta@...]
            Sent: Thursday, September 05, 2002 1:26 PM
            To: soapbuilders@yahoogroups.com
            Subject: Re: [soapbuilders] Round 4 "Fault" test endpoint

             

            I'll update the test specification to mention that env:Server is the
            expected fault code in all the faults.

            It's a good idea to define a new fault message. But can we construct
            this fault such that this also tests another aspect of fault interop.
            Another option we can change the test spec such that:

            Throws empty fault when the parameter = 1 or not 2 or not 3.
            Throws fault with a xsd:string member when the parameter =  2.
            Throws fault with a xsd:float[] member when the parameter = 3.

            Thus there is a default behavior for each method and there is out of
            range input parameter. Let me know which one you prefer ?

            Regards,
            -Arun

            Bob Cunnings wrote:

            > Hi,
            >
            > Which fault code do you want? The spec is silent on that point, but
            > I can see the case for the presumption that it's the server that's at
            > fault. It's no problem to change it.
            >
            > What is the expected behavior when an input parameter is out of
            > range?
            >
            > It might make sense to specify that env:Server is used except in
            > when an improper request is received, e.g. an input parameter is
            > out of range. Then env:client would be required. A fault message
            > might even be defined for use in such a case, perhaps echoing the
            > invalid param value, or whatever. Just a thought.
            >
            > Thanks,
            >
            > RC
            >
            > > Athough that's a good approach, but I've defined the test spec such
            > that
            > > either a fault is the only fault thrown from the method or if it's
            > > thrown along with other faults, it's thrown for the same parameter
            > value
            > > in different methods. This makes the programming little easier where
            > you
            > > may define variables at the top level and use them across different
            > > method invocations.
            > >
            > > Also, the fault codes in all your responses in env:Client instead of
            > > env:Server. Can you please check that ?
            > >
            > > Thanks,
            > > -Arun
            > >
            > > Bob Cunnings wrote:
            > >
            > > > Hi,
            > > >
            > > > Ok, I see the problem. I naively associated the fault message with
            > an input
            > > > parameter value based on the name of the fault message (e.g.
            > SimpleFault1 to
            > > > "1", but it really maps to "2"), which fails for that operation.
            > > >
            > > > The same goes for the others. I'll get this fixed later today.
            > Yes, it's
            > > > important to adhere to the spec!
            > > >
            > > > RC
            > > >
            > > >
            > > >  > Hi Bob,
            > > >  >
            > > >  > I ran JAX-RPC clients against your "fault" endpoint.
            > > >  >
            > > >  > In simple-rpc-encoded, if you can change your service
            > implementation to
            > > >  > throw faults as per the test specification at
            > > >  > http://soapinterop.java.sun.com/soapbuilders/r4/index.html then
            > > >  > echoMultipleFaults2 will throw StringFault and FloatFault in
            > the correct
            > > >  > order. Other than that all tests pass.
            > > >  >
            > > >  > Similarly some of the exceptions thrown in complex-rpc-encoded
            > are also
            > > >  > not as per the test specification.
            > > >  >
            > > >  > I know I posted the specification yesterday only, but it's
            > important
            > > >  > that we stick to that since that is the basis for us to ensure
            > correct
            > > >  > faults are thrown by the server and expected by the client
            > accordingly.
            > > >  >
            > > >  > Regards,
            > > >  > -Arun
            > > >  >
            > > >  >
            > > >
            > > >
            > > >
            > > >
            > > >
            > > > Yahoo! Groups Sponsor
            > > > ADVERTISEMENT
            > > > <
            > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=0/
            >
            > *http://geocities.yahoo.com/ps/info?.refer=blrecs

            >

            > > > <
            > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=1/
            >
            > *http://geocities.yahoo.com/ps/info?.refer=blrecs
            >

            > > >
            > > >
            > > >
            > > > -----------------------------------------------------------------
            > > > This group is a forum for builders of SOAP implementations to discuss
            > > > implementation and interoperability issues.  Please stay on-topic.
            > > >
            > > > To unsubscribe from this group, send an email to:
            > > > soapbuilders-unsubscribe@yahoogroups.com
            > > >
            > > >
            > > >
            > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
            > > > <http://docs.yahoo.com/info/terms/
            >.

            > >
            > >
            > > --
            > > =============================================
            > > There is only one me, I must live myself!
            > > There is only one today, I must live itself!
            > > =============================================
            > > http://members.tripod.com/~apgupta/index.html
            > <http://members.tripod.com/%7Eapgupta/index.html>
            > > =============================================
            > >
            > >
            > >
            > >
            > > -----------------------------------------------------------------
            > > This group is a forum for builders of SOAP implementations to
            > discuss implementation and interope
            > rability issues.  Please stay on-topic.
            > >
            > > To unsubscribe from this group, send an email to:
            > > soapbuilders-unsubscribe@yahoogroups.com
            > >
            > >
            > >
            > > Your use of Yahoo! Groups is subject to
            > http://docs.yahoo.com/info/terms/
            > >
            >
            >
            >
            > Yahoo! Groups Sponsor
            > ADVERTISEMENT
            > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
            >
            >
            >
            > -----------------------------------------------------------------
            > This group is a forum for builders of SOAP implementations to discuss
            > implementation and interoperability issues.  Please stay on-topic.
            >
            > To unsubscribe from this group, send an email to:
            > soapbuilders-unsubscribe@yahoogroups.com
            >
            >
            >
            > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
            > <http://docs.yahoo.com/info/terms/> .


            --
            =============================================
            There is only one me, I must live myself!
            There is only one today, I must live itself!
            =============================================
            http://members.tripod.com/~apgupta/index.html
            =============================================




            -----------------------------------------------------------------
            This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues.  Please stay on-topic.

            To unsubscribe from this group, send an email to:
            soapbuilders-unsubscribe@yahoogroups.com



            Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
          • Arun Gupta
            In this particular case yes, it should be an empty fault. However in other cases where there an EmptyFault is not thrown, there will be a different default
            Message 5 of 24 , Sep 5, 2002
            • 0 Attachment
              In this particular case yes, it should be an empty fault. However in
              other cases where there an EmptyFault is not thrown, there will be a
              different default behavior. I've updated the specifications at
              http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let me know
              if it looks fine.

              Thanks,
              -Arun


              Bob Cunnings wrote:

              > I like your second option, which I understand to mean that out of
              > range input values result in an empty fault. Is that correct? If so,
              > what fault code shall be used in those cases?
              >
              > RC
              >
              > > I'll update the test specification to mention that env:Server is the
              > > expected fault code in all the faults.
              > >
              > > It's a good idea to define a new fault message. But can we construct
              > > this fault such that this also tests another aspect of fault interop.
              > > Another option we can change the test spec such that:
              > >
              > > Throws empty fault when the parameter = 1 or not 2 or not 3.
              > > Throws fault with a xsd:string member when the parameter = 2.
              > > Throws fault with a xsd:float[] member when the parameter = 3.
              > >
              > > Thus there is a default behavior for each method and there is out of
              > > range input parameter. Let me know which one you prefer ?
              > >
              > > Regards,
              > > -Arun
              > >
              >
              >
              > Yahoo! Groups Sponsor
              > ADVERTISEMENT
              > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
              >
              >
              >
              > -----------------------------------------------------------------
              > This group is a forum for builders of SOAP implementations to discuss
              > implementation and interoperability issues. Please stay on-topic.
              >
              > To unsubscribe from this group, send an email to:
              > soapbuilders-unsubscribe@yahoogroups.com
              >
              >
              >
              > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
              > <http://docs.yahoo.com/info/terms/> .


              --
              =============================================
              There is only one me, I must live myself!
              There is only one today, I must live itself!
              =============================================
              http://members.tripod.com/~apgupta/index.html
              =============================================
            • Bob Cunnings
              Hi, Which fault code do you want? The spec is silent on that point, but I can see the case for the presumption that it s the server that s at fault. It s no
              Message 6 of 24 , Sep 5, 2002
              • 0 Attachment
                Hi,

                Which fault code do you want? The spec is silent on that point, but
                I can see the case for the presumption that it's the server that's at
                fault. It's no problem to change it.

                What is the expected behavior when an input parameter is out of
                range?

                It might make sense to specify that env:Server is used except in
                when an improper request is received, e.g. an input parameter is
                out of range. Then env:client would be required. A fault message
                might even be defined for use in such a case, perhaps echoing the
                invalid param value, or whatever. Just a thought.

                Thanks,

                RC

                > Athough that's a good approach, but I've defined the test spec such that
                > either a fault is the only fault thrown from the method or if it's
                > thrown along with other faults, it's thrown for the same parameter value
                > in different methods. This makes the programming little easier where you
                > may define variables at the top level and use them across different
                > method invocations.
                >
                > Also, the fault codes in all your responses in env:Client instead of
                > env:Server. Can you please check that ?
                >
                > Thanks,
                > -Arun
                >
                > Bob Cunnings wrote:
                >
                > > Hi,
                > >
                > > Ok, I see the problem. I naively associated the fault message with an input
                > > parameter value based on the name of the fault message (e.g. SimpleFault1 to
                > > "1", but it really maps to "2"), which fails for that operation.
                > >
                > > The same goes for the others. I'll get this fixed later today. Yes, it's
                > > important to adhere to the spec!
                > >
                > > RC
                > >
                > >
                > > > Hi Bob,
                > > >
                > > > I ran JAX-RPC clients against your "fault" endpoint.
                > > >
                > > > In simple-rpc-encoded, if you can change your service implementation to
                > > > throw faults as per the test specification at
                > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html then
                > > > echoMultipleFaults2 will throw StringFault and FloatFault in the correct
                > > > order. Other than that all tests pass.
                > > >
                > > > Similarly some of the exceptions thrown in complex-rpc-encoded are also
                > > > not as per the test specification.
                > > >
                > > > I know I posted the specification yesterday only, but it's important
                > > > that we stick to that since that is the basis for us to ensure correct
                > > > faults are thrown by the server and expected by the client accordingly.
                > > >
                > > > Regards,
                > > > -Arun
                > > >
                > > >
                > >
                > >
                > >
                > >
                > >
                > > Yahoo! Groups Sponsor
                > > ADVERTISEMENT
                > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=0/
                *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810373/R=1/
                *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                > >
                > >
                > >
                > > -----------------------------------------------------------------
                > > This group is a forum for builders of SOAP implementations to discuss
                > > implementation and interoperability issues. Please stay on-topic.
                > >
                > > To unsubscribe from this group, send an email to:
                > > soapbuilders-unsubscribe@yahoogroups.com
                > >
                > >
                > >
                > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                > > <http://docs.yahoo.com/info/terms/>.
                >
                >
                > --
                > =============================================
                > There is only one me, I must live myself!
                > There is only one today, I must live itself!
                > =============================================
                > http://members.tripod.com/~apgupta/index.html
                > =============================================
                >
                >
                >
                >
                > -----------------------------------------------------------------
                > This group is a forum for builders of SOAP implementations to discuss implementation and interope
                rability issues. Please stay on-topic.
                >
                > To unsubscribe from this group, send an email to:
                > soapbuilders-unsubscribe@yahoogroups.com
                >
                >
                >
                > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                >
              • Bob Cunnings
                I like your second option, which I understand to mean that out of range input values result in an empty fault. Is that correct? If so, what fault code shall be
                Message 7 of 24 , Sep 5, 2002
                • 0 Attachment
                  I like your second option, which I understand to mean that out of
                  range input values result in an empty fault. Is that correct? If so,
                  what fault code shall be used in those cases?

                  RC

                  > I'll update the test specification to mention that env:Server is the
                  > expected fault code in all the faults.
                  >
                  > It's a good idea to define a new fault message. But can we construct
                  > this fault such that this also tests another aspect of fault interop.
                  > Another option we can change the test spec such that:
                  >
                  > Throws empty fault when the parameter = 1 or not 2 or not 3.
                  > Throws fault with a xsd:string member when the parameter = 2.
                  > Throws fault with a xsd:float[] member when the parameter = 3.
                  >
                  > Thus there is a default behavior for each method and there is out of
                  > range input parameter. Let me know which one you prefer ?
                  >
                  > Regards,
                  > -Arun
                  >
                • Arun Gupta
                  All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes look fine on the first glance. I ll be doing a detailed analysis later. Do you think it
                  Message 8 of 24 , Sep 5, 2002
                  • 0 Attachment
                    All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                    look fine on the first glance. I'll be doing a detailed analysis later.

                    Do you think it makes sense to have an input parameter that can be used
                    to populate the fault detail element ? For instance, if it's a
                    StringFault, then echoStringFault will have the method operation as
                    echoStringFault(String param) and then "param" is used in the detail
                    element of fault. That way I know what exactly I'm expecting in the
                    fault detail.

                    This will need another update to your endpoints but will validate the
                    data contained within the fault. What do you say ?

                    Thanks,
                    -Arun

                    Bob Cunnings wrote:

                    > Looks fine, I've updated the WM endpoints to comply.
                    >
                    > Thanks,
                    >
                    > RC
                    >
                    > > In this particular case yes, it should be an empty fault. However in
                    > > other cases where there an EmptyFault is not thrown, there will be a
                    > > different default behavior. I've updated the specifications at
                    > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let me know
                    > > if it looks fine.
                    > >
                    > > Thanks,
                    > > -Arun
                    > >
                    > >
                    > > Bob Cunnings wrote:
                    > >
                    > > > I like your second option, which I understand to mean that out of
                    > > > range input values result in an empty fault. Is that correct? If so,
                    > > > what fault code shall be used in those cases?
                    > > >
                    > > > RC
                    > > >
                    > > > > I'll update the test specification to mention that env:Server is the
                    > > > > expected fault code in all the faults.
                    > > > >
                    > > > > It's a good idea to define a new fault message. But can we construct
                    > > > > this fault such that this also tests another aspect of fault
                    > interop.
                    > > > > Another option we can change the test spec such that:
                    > > > >
                    > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                    > > > > Throws fault with a xsd:string member when the parameter = 2.
                    > > > > Throws fault with a xsd:float[] member when the parameter = 3.
                    > > > >
                    > > > > Thus there is a default behavior for each method and there is out of
                    > > > > range input parameter. Let me know which one you prefer ?
                    > > > >
                    > > > > Regards,
                    > > > > -Arun
                    > > > >
                    > > >
                    > > >
                    > > > Yahoo! Groups Sponsor
                    > > > ADVERTISEMENT
                    > > > <
                    > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0
                    >
                    > /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                    > > >
                    > > >
                    > > >
                    > > > -----------------------------------------------------------------
                    > > > This group is a forum for builders of SOAP implementations to discuss
                    > > > implementation and interoperability issues. Please stay on-topic.
                    > > >
                    > > > To unsubscribe from this group, send an email to:
                    > > > soapbuilders-unsubscribe@yahoogroups.com
                    > > >
                    > > >
                    > > >
                    > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                    > > > <http://docs.yahoo.com/info/terms/ > .
                    > >
                    > >
                    > > --
                    > > =============================================
                    > > There is only one me, I must live myself!
                    > > There is only one today, I must live itself!
                    > > =============================================
                    > > http://members.tripod.com/~apgupta/index.html
                    > <http://members.tripod.com/%7Eapgupta/index.html>
                    > > =============================================
                    > >
                    > >
                    > >
                    > >
                    > > -----------------------------------------------------------------
                    > > This group is a forum for builders of SOAP implementations to
                    > discuss implementation and interope
                    > rability issues. Please stay on-topic.
                    > >
                    > > To unsubscribe from this group, send an email to:
                    > > soapbuilders-unsubscribe@yahoogroups.com
                    > >
                    > >
                    > >
                    > > Your use of Yahoo! Groups is subject to
                    > http://docs.yahoo.com/info/terms/
                    > >
                    > >
                    >
                    >
                    >
                    > Yahoo! Groups Sponsor
                    > ADVERTISEMENT
                    > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg>
                    > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                    >
                    > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif>
                    > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                    >
                    >
                    >
                    > -----------------------------------------------------------------
                    > This group is a forum for builders of SOAP implementations to discuss
                    > implementation and interoperability issues. Please stay on-topic.
                    >
                    > To unsubscribe from this group, send an email to:
                    > soapbuilders-unsubscribe@yahoogroups.com
                    >
                    >
                    >
                    > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                    > <http://docs.yahoo.com/info/terms/> .


                    --
                    =============================================
                    There is only one me, I must live myself!
                    There is only one today, I must live itself!
                    =============================================
                    http://members.tripod.com/~apgupta/index.html
                    =============================================
                  • Bob Cunnings
                    Looks fine, I ve updated the WM endpoints to comply. Thanks, RC ... /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ ... rability issues. Please stay
                    Message 9 of 24 , Sep 5, 2002
                    • 0 Attachment
                      Looks fine, I've updated the WM endpoints to comply.

                      Thanks,

                      RC

                      > In this particular case yes, it should be an empty fault. However in
                      > other cases where there an EmptyFault is not thrown, there will be a
                      > different default behavior. I've updated the specifications at
                      > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let me know
                      > if it looks fine.
                      >
                      > Thanks,
                      > -Arun
                      >
                      >
                      > Bob Cunnings wrote:
                      >
                      > > I like your second option, which I understand to mean that out of
                      > > range input values result in an empty fault. Is that correct? If so,
                      > > what fault code shall be used in those cases?
                      > >
                      > > RC
                      > >
                      > > > I'll update the test specification to mention that env:Server is the
                      > > > expected fault code in all the faults.
                      > > >
                      > > > It's a good idea to define a new fault message. But can we construct
                      > > > this fault such that this also tests another aspect of fault interop.
                      > > > Another option we can change the test spec such that:
                      > > >
                      > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                      > > > Throws fault with a xsd:string member when the parameter = 2.
                      > > > Throws fault with a xsd:float[] member when the parameter = 3.
                      > > >
                      > > > Thus there is a default behavior for each method and there is out of
                      > > > range input parameter. Let me know which one you prefer ?
                      > > >
                      > > > Regards,
                      > > > -Arun
                      > > >
                      > >
                      > >
                      > > Yahoo! Groups Sponsor
                      > > ADVERTISEMENT
                      > > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0
                      /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
                      > >
                      > >
                      > >
                      > > -----------------------------------------------------------------
                      > > This group is a forum for builders of SOAP implementations to discuss
                      > > implementation and interoperability issues. Please stay on-topic.
                      > >
                      > > To unsubscribe from this group, send an email to:
                      > > soapbuilders-unsubscribe@yahoogroups.com
                      > >
                      > >
                      > >
                      > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                      > > <http://docs.yahoo.com/info/terms/> .
                      >
                      >
                      > --
                      > =============================================
                      > There is only one me, I must live myself!
                      > There is only one today, I must live itself!
                      > =============================================
                      > http://members.tripod.com/~apgupta/index.html
                      > =============================================
                      >
                      >
                      >
                      >
                      > -----------------------------------------------------------------
                      > This group is a forum for builders of SOAP implementations to discuss implementation and interope
                      rability issues. Please stay on-topic.
                      >
                      > To unsubscribe from this group, send an email to:
                      > soapbuilders-unsubscribe@yahoogroups.com
                      >
                      >
                      >
                      > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                      >
                      >
                    • Arun Gupta
                      Sounds look a plan to me. I ll modify the WSDLs and update them either later today or tomorrow morning. Thanks, -Arun ... --
                      Message 10 of 24 , Sep 5, 2002
                      • 0 Attachment
                        Sounds look a plan to me. I'll modify the WSDLs and update them either
                        later today or tomorrow morning.

                        Thanks,
                        -Arun

                        Bob Cunnings wrote:

                        > I think it's a good idea, it would be easy to do. In the case of arrays
                        > how about having the input message specify the number of items in
                        > the returned array as well as the value to be used for the items?
                        > (one value would be repeated n times) Otherwise the array size will
                        > have to be fixed in the spec or left to the whim of the receiver.This
                        > expands the size of the input messages, e.g.
                        > "echoExtendedStructFault" would require 6 input params, one for
                        > the size and 5 to define the struct members. However, like you
                        > say, it's always satisfying to see the request data echoed in the
                        > reponse for validation purposes.
                        >
                        > RC
                        >
                        > > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                        > > look fine on the first glance. I'll be doing a detailed analysis later.
                        > >
                        > > Do you think it makes sense to have an input parameter that can be used
                        > > to populate the fault detail element ? For instance, if it's a
                        > > StringFault, then echoStringFault will have the method operation as
                        > > echoStringFault(String param) and then "param" is used in the detail
                        > > element of fault. That way I know what exactly I'm expecting in the
                        > > fault detail.
                        > >
                        > > This will need another update to your endpoints but will validate the
                        > > data contained within the fault. What do you say ?
                        > >
                        > > Thanks,
                        > > -Arun
                        > >
                        > > Bob Cunnings wrote:
                        > >
                        > > > Looks fine, I've updated the WM endpoints to comply.
                        > > >
                        > > > Thanks,
                        > > >
                        > > > RC
                        > > >
                        > > > > In this particular case yes, it should be an empty fault. However in
                        > > > > other cases where there an EmptyFault is not thrown, there will be a
                        > > > > different default behavior. I've updated the specifications at
                        > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                        > me know
                        > > > > if it looks fine.
                        > > > >
                        > > > > Thanks,
                        > > > > -Arun
                        > > > >
                        > > > >
                        > > > > Bob Cunnings wrote:
                        > > > >
                        > > > > > I like your second option, which I understand to mean that out of
                        > > > > > range input values result in an empty fault. Is that correct?
                        > If so,
                        > > > > > what fault code shall be used in those cases?
                        > > > > >
                        > > > > > RC
                        > > > > >
                        > > > > > > I'll update the test specification to mention that
                        > env:Server is the
                        > > > > > > expected fault code in all the faults.
                        > > > > > >
                        > > > > > > It's a good idea to define a new fault message. But can we
                        > construct
                        > > > > > > this fault such that this also tests another aspect of fault
                        > > > interop.
                        > > > > > > Another option we can change the test spec such that:
                        > > > > > >
                        > > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                        > > > > > > Throws fault with a xsd:string member when the parameter = 2.
                        > > > > > > Throws fault with a xsd:float[] member when the parameter = 3.
                        > > > > > >
                        > > > > > > Thus there is a default behavior for each method and there
                        > is out of
                        > > > > > > range input parameter. Let me know which one you prefer ?
                        > > > > > >
                        > > > > > > Regards,
                        > > > > > > -Arun
                        > > > > > >
                        > > > > >
                        > > > > >
                        > > > > > Yahoo! Groups Sponsor
                        > > > > > ADVERTISEMENT
                        > > > > > <
                        > > >
                        > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0
                        >
                        >
                        > > >
                        > > > /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                        > > > > >
                        > > > > >
                        > > > > >
                        > > > > > -----------------------------------------------------------------
                        > > > > > This group is a forum for builders of SOAP implementations to
                        > discuss
                        > > > > > implementation and interoperability issues. Please stay on-topic.
                        > > > > >
                        > > > > > To unsubscribe from this group, send an email to:
                        > > > > > soapbuilders-unsubscribe@yahoogroups.com
                        > > > > >
                        > > > > >
                        > > > > >
                        > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                        > Service
                        > > > > > <http://docs.yahoo.com/info/terms/ > .
                        > > > >
                        > > > >
                        > > > > --
                        > > > > =============================================
                        > > > > There is only one me, I must live myself!
                        > > > > There is only one today, I must live itself!
                        > > > > =============================================
                        > > > > http://members.tripod.com/~apgupta/index.html
                        > <http://members.tripod.com/%7Eapgupta/index.html>
                        > > > < http://members.tripod.com/%7Eapgupta/index.html >
                        > > > > =============================================
                        > > > >
                        > > > >
                        > > > >
                        > > > >
                        > > > > -----------------------------------------------------------------
                        > > > > This group is a forum for builders of SOAP implementations to
                        > > > discuss implementation and interope
                        > > > rability issues. Please stay on-topic.
                        > > > >
                        > > > > To unsubscribe from this group, send an email to:
                        > > > > soapbuilders-unsubscribe@yahoogroups.com
                        > > > >
                        > > > >
                        > > > >
                        > > > > Your use of Yahoo! Groups is subject to
                        > > > http://docs.yahoo.com/info/terms/
                        > > > >
                        > > > >
                        > > >
                        > > >
                        > > >
                        > > > Yahoo! Groups Sponsor
                        > > > ADVERTISEMENT
                        > > > <
                        > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                        > > > <
                        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/
                        >
                        > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                        > > >
                        > > > <
                        > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                        > > > <
                        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/
                        >
                        > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                        > > >
                        > > >
                        > > >
                        > > > -----------------------------------------------------------------
                        > > > This group is a forum for builders of SOAP implementations to discuss
                        > > > implementation and interoperability issues. Please stay on-topic.
                        > > >
                        > > > To unsubscribe from this group, send an email to:
                        > > > soapbuilders-unsubscribe@yahoogroups.com
                        > > >
                        > > >
                        > > >
                        > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                        > > > <http://docs.yahoo.com/info/terms/ > .
                        > >
                        > >
                        > > --
                        > > =============================================
                        > > There is only one me, I must live myself!
                        > > There is only one today, I must live itself!
                        > > =============================================
                        > > http://members.tripod.com/~apgupta/index.html
                        > <http://members.tripod.com/%7Eapgupta/index.html>
                        > > =============================================
                        > >
                        > >
                        > >
                        > >
                        > > -----------------------------------------------------------------
                        > > This group is a forum for builders of SOAP implementations to
                        > discuss implementation and interope
                        > rability issues. Please stay on-topic.
                        > >
                        > > To unsubscribe from this group, send an email to:
                        > > soapbuilders-unsubscribe@yahoogroups.com
                        > >
                        > >
                        > >
                        > > Your use of Yahoo! Groups is subject to
                        > http://docs.yahoo.com/info/terms/
                        > >
                        > >
                        >
                        >
                        >
                        > Yahoo! Groups Sponsor
                        > ADVERTISEMENT
                        > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189558/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/>
                        >
                        >
                        >
                        > -----------------------------------------------------------------
                        > This group is a forum for builders of SOAP implementations to discuss
                        > implementation and interoperability issues. Please stay on-topic.
                        >
                        > To unsubscribe from this group, send an email to:
                        > soapbuilders-unsubscribe@yahoogroups.com
                        >
                        >
                        >
                        > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                        > <http://docs.yahoo.com/info/terms/> .


                        --
                        =============================================
                        There is only one me, I must live myself!
                        There is only one today, I must live itself!
                        =============================================
                        http://members.tripod.com/~apgupta/index.html
                        =============================================
                      • Bob Cunnings
                        I think it s a good idea, it would be easy to do. In the case of arrays how about having the input message specify the number of items in the returned array as
                        Message 11 of 24 , Sep 5, 2002
                        • 0 Attachment
                          I think it's a good idea, it would be easy to do. In the case of arrays
                          how about having the input message specify the number of items in
                          the returned array as well as the value to be used for the items?
                          (one value would be repeated n times) Otherwise the array size will
                          have to be fixed in the spec or left to the whim of the receiver.This
                          expands the size of the input messages, e.g.
                          "echoExtendedStructFault" would require 6 input params, one for
                          the size and 5 to define the struct members. However, like you
                          say, it's always satisfying to see the request data echoed in the
                          reponse for validation purposes.

                          RC

                          > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                          > look fine on the first glance. I'll be doing a detailed analysis later.
                          >
                          > Do you think it makes sense to have an input parameter that can be used
                          > to populate the fault detail element ? For instance, if it's a
                          > StringFault, then echoStringFault will have the method operation as
                          > echoStringFault(String param) and then "param" is used in the detail
                          > element of fault. That way I know what exactly I'm expecting in the
                          > fault detail.
                          >
                          > This will need another update to your endpoints but will validate the
                          > data contained within the fault. What do you say ?
                          >
                          > Thanks,
                          > -Arun
                          >
                          > Bob Cunnings wrote:
                          >
                          > > Looks fine, I've updated the WM endpoints to comply.
                          > >
                          > > Thanks,
                          > >
                          > > RC
                          > >
                          > > > In this particular case yes, it should be an empty fault. However in
                          > > > other cases where there an EmptyFault is not thrown, there will be a
                          > > > different default behavior. I've updated the specifications at
                          > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let me know
                          > > > if it looks fine.
                          > > >
                          > > > Thanks,
                          > > > -Arun
                          > > >
                          > > >
                          > > > Bob Cunnings wrote:
                          > > >
                          > > > > I like your second option, which I understand to mean that out of
                          > > > > range input values result in an empty fault. Is that correct? If so,
                          > > > > what fault code shall be used in those cases?
                          > > > >
                          > > > > RC
                          > > > >
                          > > > > > I'll update the test specification to mention that env:Server is the
                          > > > > > expected fault code in all the faults.
                          > > > > >
                          > > > > > It's a good idea to define a new fault message. But can we construct
                          > > > > > this fault such that this also tests another aspect of fault
                          > > interop.
                          > > > > > Another option we can change the test spec such that:
                          > > > > >
                          > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                          > > > > > Throws fault with a xsd:string member when the parameter = 2.
                          > > > > > Throws fault with a xsd:float[] member when the parameter = 3.
                          > > > > >
                          > > > > > Thus there is a default behavior for each method and there is out of
                          > > > > > range input parameter. Let me know which one you prefer ?
                          > > > > >
                          > > > > > Regards,
                          > > > > > -Arun
                          > > > > >
                          > > > >
                          > > > >
                          > > > > Yahoo! Groups Sponsor
                          > > > > ADVERTISEMENT
                          > > > > <
                          > > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0

                          > >
                          > > /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                          > > > >
                          > > > >
                          > > > >
                          > > > > -----------------------------------------------------------------
                          > > > > This group is a forum for builders of SOAP implementations to discuss
                          > > > > implementation and interoperability issues. Please stay on-topic.
                          > > > >
                          > > > > To unsubscribe from this group, send an email to:
                          > > > > soapbuilders-unsubscribe@yahoogroups.com
                          > > > >
                          > > > >
                          > > > >
                          > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                          > > > > <http://docs.yahoo.com/info/terms/ > .
                          > > >
                          > > >
                          > > > --
                          > > > =============================================
                          > > > There is only one me, I must live myself!
                          > > > There is only one today, I must live itself!
                          > > > =============================================
                          > > > http://members.tripod.com/~apgupta/index.html
                          > > <http://members.tripod.com/%7Eapgupta/index.html>
                          > > > =============================================
                          > > >
                          > > >
                          > > >
                          > > >
                          > > > -----------------------------------------------------------------
                          > > > This group is a forum for builders of SOAP implementations to
                          > > discuss implementation and interope
                          > > rability issues. Please stay on-topic.
                          > > >
                          > > > To unsubscribe from this group, send an email to:
                          > > > soapbuilders-unsubscribe@yahoogroups.com
                          > > >
                          > > >
                          > > >
                          > > > Your use of Yahoo! Groups is subject to
                          > > http://docs.yahoo.com/info/terms/
                          > > >
                          > > >
                          > >
                          > >
                          > >
                          > > Yahoo! Groups Sponsor
                          > > ADVERTISEMENT
                          > > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg>
                          > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/
                          *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                          > >
                          > > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif>
                          > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/
                          *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                          > >
                          > >
                          > >
                          > > -----------------------------------------------------------------
                          > > This group is a forum for builders of SOAP implementations to discuss
                          > > implementation and interoperability issues. Please stay on-topic.
                          > >
                          > > To unsubscribe from this group, send an email to:
                          > > soapbuilders-unsubscribe@yahoogroups.com
                          > >
                          > >
                          > >
                          > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                          > > <http://docs.yahoo.com/info/terms/> .
                          >
                          >
                          > --
                          > =============================================
                          > There is only one me, I must live myself!
                          > There is only one today, I must live itself!
                          > =============================================
                          > http://members.tripod.com/~apgupta/index.html
                          > =============================================
                          >
                          >
                          >
                          >
                          > -----------------------------------------------------------------
                          > This group is a forum for builders of SOAP implementations to discuss implementation and interope
                          rability issues. Please stay on-topic.
                          >
                          > To unsubscribe from this group, send an email to:
                          > soapbuilders-unsubscribe@yahoogroups.com
                          >
                          >
                          >
                          > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                          >
                          >
                        • Arun Gupta
                          I ve updated the WSDLs and the test specifications at http://soapinterop.java.sun.com/soapbuilders/r4/index.html. I ve restructured some of the tests and
                          Message 12 of 24 , Sep 6, 2002
                          • 0 Attachment
                            I've updated the WSDLs and the test specifications at
                            http://soapinterop.java.sun.com/soapbuilders/r4/index.html.

                            I've restructured some of the tests and removed a not-so-realistic use
                            case from complex-rpc-encoded/doc-literal. Let me know if it needs
                            further clarification.

                            Have a nice weekend!
                            -Arun

                            Bob Cunnings wrote:

                            > I think it's a good idea, it would be easy to do. In the case of arrays
                            > how about having the input message specify the number of items in
                            > the returned array as well as the value to be used for the items?
                            > (one value would be repeated n times) Otherwise the array size will
                            > have to be fixed in the spec or left to the whim of the receiver.This
                            > expands the size of the input messages, e.g.
                            > "echoExtendedStructFault" would require 6 input params, one for
                            > the size and 5 to define the struct members. However, like you
                            > say, it's always satisfying to see the request data echoed in the
                            > reponse for validation purposes.
                            >
                            > RC
                            >
                            > > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                            > > look fine on the first glance. I'll be doing a detailed analysis later.
                            > >
                            > > Do you think it makes sense to have an input parameter that can be used
                            > > to populate the fault detail element ? For instance, if it's a
                            > > StringFault, then echoStringFault will have the method operation as
                            > > echoStringFault(String param) and then "param" is used in the detail
                            > > element of fault. That way I know what exactly I'm expecting in the
                            > > fault detail.
                            > >
                            > > This will need another update to your endpoints but will validate the
                            > > data contained within the fault. What do you say ?
                            > >
                            > > Thanks,
                            > > -Arun
                            > >
                            > > Bob Cunnings wrote:
                            > >
                            > > > Looks fine, I've updated the WM endpoints to comply.
                            > > >
                            > > > Thanks,
                            > > >
                            > > > RC
                            > > >
                            > > > > In this particular case yes, it should be an empty fault. However in
                            > > > > other cases where there an EmptyFault is not thrown, there will be a
                            > > > > different default behavior. I've updated the specifications at
                            > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                            > me know
                            > > > > if it looks fine.
                            > > > >
                            > > > > Thanks,
                            > > > > -Arun
                            > > > >
                            > > > >
                            > > > > Bob Cunnings wrote:
                            > > > >
                            > > > > > I like your second option, which I understand to mean that out of
                            > > > > > range input values result in an empty fault. Is that correct?
                            > If so,
                            > > > > > what fault code shall be used in those cases?
                            > > > > >
                            > > > > > RC
                            > > > > >
                            > > > > > > I'll update the test specification to mention that
                            > env:Server is the
                            > > > > > > expected fault code in all the faults.
                            > > > > > >
                            > > > > > > It's a good idea to define a new fault message. But can we
                            > construct
                            > > > > > > this fault such that this also tests another aspect of fault
                            > > > interop.
                            > > > > > > Another option we can change the test spec such that:
                            > > > > > >
                            > > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                            > > > > > > Throws fault with a xsd:string member when the parameter = 2.
                            > > > > > > Throws fault with a xsd:float[] member when the parameter = 3.
                            > > > > > >
                            > > > > > > Thus there is a default behavior for each method and there
                            > is out of
                            > > > > > > range input parameter. Let me know which one you prefer ?
                            > > > > > >
                            > > > > > > Regards,
                            > > > > > > -Arun
                            > > > > > >
                            > > > > >
                            > > > > >
                            > > > > > Yahoo! Groups Sponsor
                            > > > > > ADVERTISEMENT
                            > > > > > <
                            > > >
                            > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0
                            >
                            >
                            > > >
                            > > > /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                            > > > > >
                            > > > > >
                            > > > > >
                            > > > > > -----------------------------------------------------------------
                            > > > > > This group is a forum for builders of SOAP implementations to
                            > discuss
                            > > > > > implementation and interoperability issues. Please stay on-topic.
                            > > > > >
                            > > > > > To unsubscribe from this group, send an email to:
                            > > > > > soapbuilders-unsubscribe@yahoogroups.com
                            > > > > >
                            > > > > >
                            > > > > >
                            > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                            > Service
                            > > > > > <http://docs.yahoo.com/info/terms/ > .
                            > > > >
                            > > > >
                            > > > > --
                            > > > > =============================================
                            > > > > There is only one me, I must live myself!
                            > > > > There is only one today, I must live itself!
                            > > > > =============================================
                            > > > > http://members.tripod.com/~apgupta/index.html
                            > <http://members.tripod.com/%7Eapgupta/index.html>
                            > > > < http://members.tripod.com/%7Eapgupta/index.html >
                            > > > > =============================================
                            > > > >
                            > > > >
                            > > > >
                            > > > >
                            > > > > -----------------------------------------------------------------
                            > > > > This group is a forum for builders of SOAP implementations to
                            > > > discuss implementation and interope
                            > > > rability issues. Please stay on-topic.
                            > > > >
                            > > > > To unsubscribe from this group, send an email to:
                            > > > > soapbuilders-unsubscribe@yahoogroups.com
                            > > > >
                            > > > >
                            > > > >
                            > > > > Your use of Yahoo! Groups is subject to
                            > > > http://docs.yahoo.com/info/terms/
                            > > > >
                            > > > >
                            > > >
                            > > >
                            > > >
                            > > > Yahoo! Groups Sponsor
                            > > > ADVERTISEMENT
                            > > > <
                            > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                            > > > <
                            > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/
                            >
                            > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                            > > >
                            > > > <
                            > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                            > > > <
                            > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/
                            >
                            > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                            > > >
                            > > >
                            > > >
                            > > > -----------------------------------------------------------------
                            > > > This group is a forum for builders of SOAP implementations to discuss
                            > > > implementation and interoperability issues. Please stay on-topic.
                            > > >
                            > > > To unsubscribe from this group, send an email to:
                            > > > soapbuilders-unsubscribe@yahoogroups.com
                            > > >
                            > > >
                            > > >
                            > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                            > > > <http://docs.yahoo.com/info/terms/ > .
                            > >
                            > >
                            > > --
                            > > =============================================
                            > > There is only one me, I must live myself!
                            > > There is only one today, I must live itself!
                            > > =============================================
                            > > http://members.tripod.com/~apgupta/index.html
                            > <http://members.tripod.com/%7Eapgupta/index.html>
                            > > =============================================
                            > >
                            > >
                            > >
                            > >
                            > > -----------------------------------------------------------------
                            > > This group is a forum for builders of SOAP implementations to
                            > discuss implementation and interope
                            > rability issues. Please stay on-topic.
                            > >
                            > > To unsubscribe from this group, send an email to:
                            > > soapbuilders-unsubscribe@yahoogroups.com
                            > >
                            > >
                            > >
                            > > Your use of Yahoo! Groups is subject to
                            > http://docs.yahoo.com/info/terms/
                            > >
                            > >
                            >
                            >
                            >
                            > Yahoo! Groups Sponsor
                            > ADVERTISEMENT
                            > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189558/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/>
                            >
                            >
                            >
                            > -----------------------------------------------------------------
                            > This group is a forum for builders of SOAP implementations to discuss
                            > implementation and interoperability issues. Please stay on-topic.
                            >
                            > To unsubscribe from this group, send an email to:
                            > soapbuilders-unsubscribe@yahoogroups.com
                            >
                            >
                            >
                            > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                            > <http://docs.yahoo.com/info/terms/> .


                            --
                            =============================================
                            There is only one me, I must live myself!
                            There is only one today, I must live itself!
                            =============================================
                            http://members.tripod.com/~apgupta/index.html
                            =============================================
                          • Bob Cunnings
                            Re: simple-rpc-encoded Operation echoMultipleFaults3 has two string input parameters, and the possible fault messages consist of a single string. Which
                            Message 13 of 24 , Sep 7, 2002
                            • 0 Attachment
                              Re: "simple-rpc-encoded"

                              Operation "echoMultipleFaults3" has two string input parameters, and the
                              possible fault messages consist of a single string. Which input parameter is
                              to be echoed in the fault message for the different "whichFault" cases?

                              RC

                              > I've updated the WSDLs and the test specifications at
                              > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                              >
                              > I've restructured some of the tests and removed a not-so-realistic use
                              > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                              > further clarification.
                              >
                              > Have a nice weekend!
                              > -Arun
                              >
                            • Bob Cunnings
                              Re: complex-rpc-encoded There is a discrepency between the prose specification and the WSDL definitions for operations echoMultipleFaults1 and
                              Message 14 of 24 , Sep 7, 2002
                              • 0 Attachment
                                Re: complex-rpc-encoded

                                There is a discrepency between the prose specification and the WSDL
                                definitions for operations "echoMultipleFaults1" and "echoMultipleFaults2".
                                I am proceeding on the assumption that the WSDL is correct and that control
                                parameter "1" results in ComplexFault1, and so on.

                                RC

                                > I've updated the WSDLs and the test specifications at
                                > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                                >
                                > I've restructured some of the tests and removed a not-so-realistic use
                                > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                                > further clarification.
                                >
                                > Have a nice weekend!
                                > -Arun
                                >
                                > Bob Cunnings wrote:
                                >
                                > > I think it's a good idea, it would be easy to do. In the case of arrays
                                > > how about having the input message specify the number of items in
                                > > the returned array as well as the value to be used for the items?
                                > > (one value would be repeated n times) Otherwise the array size will
                                > > have to be fixed in the spec or left to the whim of the receiver.This
                                > > expands the size of the input messages, e.g.
                                > > "echoExtendedStructFault" would require 6 input params, one for
                                > > the size and 5 to define the struct members. However, like you
                                > > say, it's always satisfying to see the request data echoed in the
                                > > reponse for validation purposes.
                                > >
                                > > RC
                                > >
                                > > > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                                > > > look fine on the first glance. I'll be doing a detailed analysis
                                later.
                                > > >
                                > > > Do you think it makes sense to have an input parameter that can be
                                used
                                > > > to populate the fault detail element ? For instance, if it's a
                                > > > StringFault, then echoStringFault will have the method operation as
                                > > > echoStringFault(String param) and then "param" is used in the detail
                                > > > element of fault. That way I know what exactly I'm expecting in the
                                > > > fault detail.
                                > > >
                                > > > This will need another update to your endpoints but will validate the
                                > > > data contained within the fault. What do you say ?
                                > > >
                                > > > Thanks,
                                > > > -Arun
                                > > >
                                > > > Bob Cunnings wrote:
                                > > >
                                > > > > Looks fine, I've updated the WM endpoints to comply.
                                > > > >
                                > > > > Thanks,
                                > > > >
                                > > > > RC
                                > > > >
                                > > > > > In this particular case yes, it should be an empty fault. However
                                in
                                > > > > > other cases where there an EmptyFault is not thrown, there will be
                                a
                                > > > > > different default behavior. I've updated the specifications at
                                > > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                                > > me know
                                > > > > > if it looks fine.
                                > > > > >
                                > > > > > Thanks,
                                > > > > > -Arun
                                > > > > >
                                > > > > >
                                > > > > > Bob Cunnings wrote:
                                > > > > >
                                > > > > > > I like your second option, which I understand to mean that out
                                of
                                > > > > > > range input values result in an empty fault. Is that correct?
                                > > If so,
                                > > > > > > what fault code shall be used in those cases?
                                > > > > > >
                                > > > > > > RC
                                > > > > > >
                                > > > > > > > I'll update the test specification to mention that
                                > > env:Server is the
                                > > > > > > > expected fault code in all the faults.
                                > > > > > > >
                                > > > > > > > It's a good idea to define a new fault message. But can we
                                > > construct
                                > > > > > > > this fault such that this also tests another aspect of fault
                                > > > > interop.
                                > > > > > > > Another option we can change the test spec such that:
                                > > > > > > >
                                > > > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                                > > > > > > > Throws fault with a xsd:string member when the parameter = 2.
                                > > > > > > > Throws fault with a xsd:float[] member when the parameter = 3.
                                > > > > > > >
                                > > > > > > > Thus there is a default behavior for each method and there
                                > > is out of
                                > > > > > > > range input parameter. Let me know which one you prefer ?
                                > > > > > > >
                                > > > > > > > Regards,
                                > > > > > > > -Arun
                                > > > > > > >
                                > > > > > >
                                > > > > > >
                                > > > > > > Yahoo! Groups Sponsor
                                > > > > > > ADVERTISEMENT
                                > > > > > > <
                                > > > >
                                > >
                                http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=170570101
                                4:HM/A=1189560/R=0
                                > >
                                > >
                                > > > >
                                > > > > /*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                                > > > > > >
                                > > > > > >
                                > > > > > >
                                > > > > >
                                > -----------------------------------------------------------------
                                > > > > > > This group is a forum for builders of SOAP implementations to
                                > > discuss
                                > > > > > > implementation and interoperability issues. Please stay
                                on-topic.
                                > > > > > >
                                > > > > > > To unsubscribe from this group, send an email to:
                                > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                > > > > > >
                                > > > > > >
                                > > > > > >
                                > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                > > Service
                                > > > > > > <http://docs.yahoo.com/info/terms/ > .
                                > > > > >
                                > > > > >
                                > > > > > --
                                > > > > > =============================================
                                > > > > > There is only one me, I must live myself!
                                > > > > > There is only one today, I must live itself!
                                > > > > > =============================================
                                > > > > > http://members.tripod.com/~apgupta/index.html
                                > > <http://members.tripod.com/%7Eapgupta/index.html>
                                > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                > > > > > =============================================
                                > > > > >
                                > > > > >
                                > > > > >
                                > > > > >
                                > > > > > -----------------------------------------------------------------
                                > > > > > This group is a forum for builders of SOAP implementations to
                                > > > > discuss implementation and interope
                                > > > > rability issues. Please stay on-topic.
                                > > > > >
                                > > > > > To unsubscribe from this group, send an email to:
                                > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                > > > > >
                                > > > > >
                                > > > > >
                                > > > > > Your use of Yahoo! Groups is subject to
                                > > > > http://docs.yahoo.com/info/terms/
                                > > > > >
                                > > > > >
                                > > > >
                                > > > >
                                > > > >
                                > > > > Yahoo! Groups Sponsor
                                > > > > ADVERTISEMENT
                                > > > > <
                                > > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                                > > > > <
                                > >
                                http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                4:HM/A=810327/R=0/
                                > >
                                > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                > > > >
                                > > > > <
                                > > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                                > > > > <
                                > >
                                http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                4:HM/A=810327/R=1/
                                > >
                                > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                > > > >
                                > > > >
                                > > > >
                                > > > > -----------------------------------------------------------------
                                > > > > This group is a forum for builders of SOAP implementations to
                                discuss
                                > > > > implementation and interoperability issues. Please stay on-topic.
                                > > > >
                                > > > > To unsubscribe from this group, send an email to:
                                > > > > soapbuilders-unsubscribe@yahoogroups.com
                                > > > >
                                > > > >
                                > > > >
                                > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                > > > > <http://docs.yahoo.com/info/terms/ > .
                                > > >
                                > > >
                                > > > --
                                > > > =============================================
                                > > > There is only one me, I must live myself!
                                > > > There is only one today, I must live itself!
                                > > > =============================================
                                > > > http://members.tripod.com/~apgupta/index.html
                                > > <http://members.tripod.com/%7Eapgupta/index.html>
                                > > > =============================================
                                > > >
                                > > >
                                > > >
                                > > >
                                > > > -----------------------------------------------------------------
                                > > > This group is a forum for builders of SOAP implementations to
                                > > discuss implementation and interope
                                > > rability issues. Please stay on-topic.
                                > > >
                                > > > To unsubscribe from this group, send an email to:
                                > > > soapbuilders-unsubscribe@yahoogroups.com
                                > > >
                                > > >
                                > > >
                                > > > Your use of Yahoo! Groups is subject to
                                > > http://docs.yahoo.com/info/terms/
                                > > >
                                > > >
                                > >
                                > >
                                > >
                                > > Yahoo! Groups Sponsor
                                > > ADVERTISEMENT
                                > >
                                <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=17057010
                                14:HM/A=1189558/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/>
                                > >
                                > >
                                > >
                                > > -----------------------------------------------------------------
                                > > This group is a forum for builders of SOAP implementations to discuss
                                > > implementation and interoperability issues. Please stay on-topic.
                                > >
                                > > To unsubscribe from this group, send an email to:
                                > > soapbuilders-unsubscribe@yahoogroups.com
                                > >
                                > >
                                > >
                                > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                > > <http://docs.yahoo.com/info/terms/> .
                                >
                                >
                                > --
                                > =============================================
                                > There is only one me, I must live myself!
                                > There is only one today, I must live itself!
                                > =============================================
                                > http://members.tripod.com/~apgupta/index.html
                                > =============================================
                                >
                                >
                                >
                                >
                                > -----------------------------------------------------------------
                                > This group is a forum for builders of SOAP implementations to discuss
                                implementation and interoperability issues. Please stay on-topic.
                                >
                                > To unsubscribe from this group, send an email to:
                                > soapbuilders-unsubscribe@yahoogroups.com
                                >
                                >
                                >
                                > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                                >
                                >
                              • Bob Cunnings
                                Ok, the WM endpoints and test clients are updated to match the new definitions. An endpoint and test clients are available for the soapfault tests also,
                                Message 15 of 24 , Sep 8, 2002
                                • 0 Attachment
                                  Ok, the WM endpoints and test clients are updated to match the new
                                  definitions. An endpoint and test clients are available for the "soapfault"
                                  tests also, linked to from the round 4 page [1].

                                  Something to bear in mind when looking at wire dumps:
                                  In "complex-rpc-encoded", operations "echoSOAPStructFault" and
                                  "echoMultipleFaults1" differ in the way the SOAPStruct value is passed in
                                  the request message. According to the WSDL, message
                                  "echoSOAPStructFaultRequest" uses a part (parameter) of type
                                  "SOAPStructFault" to carry the struct value whereas message
                                  "echoMultipleFaults1Request" uses a part of type "SOAPStruct" to do the
                                  same.

                                  RC

                                  [1] http://www.whitemesa.net/r4/interop4.html

                                  > I've updated the WSDLs and the test specifications at
                                  > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                                  >
                                  > I've restructured some of the tests and removed a not-so-realistic use
                                  > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                                  > further clarification.
                                  >
                                  > Have a nice weekend!
                                  > -Arun
                                  >
                                • Arun Gupta
                                  I ve updated the test description to be in sync with the WSDL for complex-rpc-encoded. Re: simple-rpc-encoded, SimpleFault1 needs to be thrown when
                                  Message 16 of 24 , Sep 9, 2002
                                  • 0 Attachment
                                    I've updated the test description to be in sync with the WSDL for
                                    complex-rpc-encoded.

                                    Re: simple-rpc-encoded, SimpleFault1 needs to be thrown when
                                    "whichFault" is 1 or not 2 and SimpleFault2 when "whichFault" is 2. This
                                    was also mentioned in the document. Do you want me to clarify it any
                                    further ?

                                    Thanks,
                                    -Arun

                                    Bob Cunnings wrote:

                                    > Re: complex-rpc-encoded
                                    >
                                    > There is a discrepency between the prose specification and the WSDL
                                    > definitions for operations "echoMultipleFaults1" and
                                    > "echoMultipleFaults2".
                                    > I am proceeding on the assumption that the WSDL is correct and that
                                    > control
                                    > parameter "1" results in ComplexFault1, and so on.
                                    >
                                    > RC
                                    >
                                    > > I've updated the WSDLs and the test specifications at
                                    > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                                    > >
                                    > > I've restructured some of the tests and removed a not-so-realistic use
                                    > > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                                    > > further clarification.
                                    > >
                                    > > Have a nice weekend!
                                    > > -Arun
                                    > >
                                    > > Bob Cunnings wrote:
                                    > >
                                    > > > I think it's a good idea, it would be easy to do. In the case of
                                    > arrays
                                    > > > how about having the input message specify the number of items in
                                    > > > the returned array as well as the value to be used for the items?
                                    > > > (one value would be repeated n times) Otherwise the array size will
                                    > > > have to be fixed in the spec or left to the whim of the receiver.This
                                    > > > expands the size of the input messages, e.g.
                                    > > > "echoExtendedStructFault" would require 6 input params, one for
                                    > > > the size and 5 to define the struct members. However, like you
                                    > > > say, it's always satisfying to see the request data echoed in the
                                    > > > reponse for validation purposes.
                                    > > >
                                    > > > RC
                                    > > >
                                    > > > > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                                    > > > > look fine on the first glance. I'll be doing a detailed analysis
                                    > later.
                                    > > > >
                                    > > > > Do you think it makes sense to have an input parameter that can be
                                    > used
                                    > > > > to populate the fault detail element ? For instance, if it's a
                                    > > > > StringFault, then echoStringFault will have the method operation as
                                    > > > > echoStringFault(String param) and then "param" is used in the detail
                                    > > > > element of fault. That way I know what exactly I'm expecting in the
                                    > > > > fault detail.
                                    > > > >
                                    > > > > This will need another update to your endpoints but will
                                    > validate the
                                    > > > > data contained within the fault. What do you say ?
                                    > > > >
                                    > > > > Thanks,
                                    > > > > -Arun
                                    > > > >
                                    > > > > Bob Cunnings wrote:
                                    > > > >
                                    > > > > > Looks fine, I've updated the WM endpoints to comply.
                                    > > > > >
                                    > > > > > Thanks,
                                    > > > > >
                                    > > > > > RC
                                    > > > > >
                                    > > > > > > In this particular case yes, it should be an empty fault.
                                    > However
                                    > in
                                    > > > > > > other cases where there an EmptyFault is not thrown, there
                                    > will be
                                    > a
                                    > > > > > > different default behavior. I've updated the specifications at
                                    > > > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                                    > > > me know
                                    > > > > > > if it looks fine.
                                    > > > > > >
                                    > > > > > > Thanks,
                                    > > > > > > -Arun
                                    > > > > > >
                                    > > > > > >
                                    > > > > > > Bob Cunnings wrote:
                                    > > > > > >
                                    > > > > > > > I like your second option, which I understand to mean that out
                                    > of
                                    > > > > > > > range input values result in an empty fault. Is that correct?
                                    > > > If so,
                                    > > > > > > > what fault code shall be used in those cases?
                                    > > > > > > >
                                    > > > > > > > RC
                                    > > > > > > >
                                    > > > > > > > > I'll update the test specification to mention that
                                    > > > env:Server is the
                                    > > > > > > > > expected fault code in all the faults.
                                    > > > > > > > >
                                    > > > > > > > > It's a good idea to define a new fault message. But can we
                                    > > > construct
                                    > > > > > > > > this fault such that this also tests another aspect of fault
                                    > > > > > interop.
                                    > > > > > > > > Another option we can change the test spec such that:
                                    > > > > > > > >
                                    > > > > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                                    > > > > > > > > Throws fault with a xsd:string member when the parameter
                                    > = 2.
                                    > > > > > > > > Throws fault with a xsd:float[] member when the
                                    > parameter = 3.
                                    > > > > > > > >
                                    > > > > > > > > Thus there is a default behavior for each method and there
                                    > > > is out of
                                    > > > > > > > > range input parameter. Let me know which one you prefer ?
                                    > > > > > > > >
                                    > > > > > > > > Regards,
                                    > > > > > > > > -Arun
                                    > > > > > > > >
                                    > > > > > > >
                                    > > > > > > >
                                    > > > > > > > Yahoo! Groups Sponsor
                                    > > > > > > > ADVERTISEMENT
                                    > > > > > > > <
                                    > > > > >
                                    > > >
                                    > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=170570101
                                    >
                                    > 4:HM/A=1189560/R=0
                                    > > >
                                    > > >
                                    > > > > >
                                    > > > > > /* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                                    > > > > > > >
                                    > > > > > > >
                                    > > > > > > >
                                    > > > > > >
                                    > > -----------------------------------------------------------------
                                    > > > > > > > This group is a forum for builders of SOAP implementations to
                                    > > > discuss
                                    > > > > > > > implementation and interoperability issues. Please stay
                                    > on-topic.
                                    > > > > > > >
                                    > > > > > > > To unsubscribe from this group, send an email to:
                                    > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                    > > > > > > >
                                    > > > > > > >
                                    > > > > > > >
                                    > > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                    > > > Service
                                    > > > > > > > < http://docs.yahoo.com/info/terms/ > .
                                    > > > > > >
                                    > > > > > >
                                    > > > > > > --
                                    > > > > > > =============================================
                                    > > > > > > There is only one me, I must live myself!
                                    > > > > > > There is only one today, I must live itself!
                                    > > > > > > =============================================
                                    > > > > > > http://members.tripod.com/~apgupta/index.html
                                    > <http://members.tripod.com/%7Eapgupta/index.html>
                                    > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                    > > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                    > > > > > > =============================================
                                    > > > > > >
                                    > > > > > >
                                    > > > > > >
                                    > > > > > >
                                    > > > > > >
                                    > -----------------------------------------------------------------
                                    > > > > > > This group is a forum for builders of SOAP implementations to
                                    > > > > > discuss implementation and interope
                                    > > > > > rability issues. Please stay on-topic.
                                    > > > > > >
                                    > > > > > > To unsubscribe from this group, send an email to:
                                    > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                    > > > > > >
                                    > > > > > >
                                    > > > > > >
                                    > > > > > > Your use of Yahoo! Groups is subject to
                                    > > > > > http://docs.yahoo.com/info/terms/
                                    > > > > > >
                                    > > > > > >
                                    > > > > >
                                    > > > > >
                                    > > > > >
                                    > > > > > Yahoo! Groups Sponsor
                                    > > > > > ADVERTISEMENT
                                    > > > > > <
                                    > > >
                                    > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                                    > > > > > <
                                    > > >
                                    > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                    >
                                    > 4:HM/A=810327/R=0/
                                    > > >
                                    > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                    > > > > >
                                    > > > > > <
                                    > > >
                                    > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                                    > > > > > <
                                    > > >
                                    > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                    >
                                    > 4:HM/A=810327/R=1/
                                    > > >
                                    > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                    > > > > >
                                    > > > > >
                                    > > > > >
                                    > > > > > -----------------------------------------------------------------
                                    > > > > > This group is a forum for builders of SOAP implementations to
                                    > discuss
                                    > > > > > implementation and interoperability issues. Please stay on-topic.
                                    > > > > >
                                    > > > > > To unsubscribe from this group, send an email to:
                                    > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                    > > > > >
                                    > > > > >
                                    > > > > >
                                    > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                    > Service
                                    > > > > > <http://docs.yahoo.com/info/terms/ > .
                                    > > > >
                                    > > > >
                                    > > > > --
                                    > > > > =============================================
                                    > > > > There is only one me, I must live myself!
                                    > > > > There is only one today, I must live itself!
                                    > > > > =============================================
                                    > > > > http://members.tripod.com/~apgupta/index.html
                                    > <http://members.tripod.com/%7Eapgupta/index.html>
                                    > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                    > > > > =============================================
                                    > > > >
                                    > > > >
                                    > > > >
                                    > > > >
                                    > > > > -----------------------------------------------------------------
                                    > > > > This group is a forum for builders of SOAP implementations to
                                    > > > discuss implementation and interope
                                    > > > rability issues. Please stay on-topic.
                                    > > > >
                                    > > > > To unsubscribe from this group, send an email to:
                                    > > > > soapbuilders-unsubscribe@yahoogroups.com
                                    > > > >
                                    > > > >
                                    > > > >
                                    > > > > Your use of Yahoo! Groups is subject to
                                    > > > http://docs.yahoo.com/info/terms/
                                    > > > >
                                    > > > >
                                    > > >
                                    > > >
                                    > > >
                                    > > > Yahoo! Groups Sponsor
                                    > > > ADVERTISEMENT
                                    > > >
                                    > <
                                    > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=17057010
                                    >
                                    > 14:HM/A=1189558/R=0/* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/ >
                                    > > >
                                    > > >
                                    > > >
                                    > > > -----------------------------------------------------------------
                                    > > > This group is a forum for builders of SOAP implementations to discuss
                                    > > > implementation and interoperability issues. Please stay on-topic.
                                    > > >
                                    > > > To unsubscribe from this group, send an email to:
                                    > > > soapbuilders-unsubscribe@yahoogroups.com
                                    > > >
                                    > > >
                                    > > >
                                    > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                    > > > <http://docs.yahoo.com/info/terms/ > .
                                    > >
                                    > >
                                    > > --
                                    > > =============================================
                                    > > There is only one me, I must live myself!
                                    > > There is only one today, I must live itself!
                                    > > =============================================
                                    > > http://members.tripod.com/~apgupta/index.html
                                    > <http://members.tripod.com/%7Eapgupta/index.html>
                                    > > =============================================
                                    > >
                                    > >
                                    > >
                                    > >
                                    > > -----------------------------------------------------------------
                                    > > This group is a forum for builders of SOAP implementations to discuss
                                    > implementation and interoperability issues. Please stay on-topic.
                                    > >
                                    > > To unsubscribe from this group, send an email to:
                                    > > soapbuilders-unsubscribe@yahoogroups.com
                                    > >
                                    > >
                                    > >
                                    > > Your use of Yahoo! Groups is subject to
                                    > http://docs.yahoo.com/info/terms/
                                    > >
                                    > >
                                    >
                                    >
                                    >
                                    >
                                    > Yahoo! Groups Sponsor
                                    > ADVERTISEMENT
                                    > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg>
                                    > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                    >
                                    > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif>
                                    > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                    >
                                    >
                                    >
                                    > -----------------------------------------------------------------
                                    > This group is a forum for builders of SOAP implementations to discuss
                                    > implementation and interoperability issues. Please stay on-topic.
                                    >
                                    > To unsubscribe from this group, send an email to:
                                    > soapbuilders-unsubscribe@yahoogroups.com
                                    >
                                    >
                                    >
                                    > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                    > <http://docs.yahoo.com/info/terms/> .


                                    --
                                    =============================================
                                    There is only one me, I must live myself!
                                    There is only one today, I must live itself!
                                    =============================================
                                    http://members.tripod.com/~apgupta/index.html
                                    =============================================
                                  • Bob Cunnings
                                    Yes. The input message for echoMultipleFaults3 contains 2 string parameters. The Faults that may result, SimpleFault1 and SimpleFault2 each refer to a
                                    Message 17 of 24 , Sep 9, 2002
                                    • 0 Attachment
                                      Yes.
                                      The input message for "echoMultipleFaults3" contains 2 string
                                      parameters. The Faults that may result, "SimpleFault1" and
                                      "SimpleFault2" each refer to a fault message containing a single
                                      string. The question is, what is the connection between input string
                                      parameters and the fault messages? Which of the input strings,
                                      param1 or param2, is expected to be echoed in the fault message
                                      when "whichFault" is 1 (or not 2), and when "whichFault" is 2?

                                      RC

                                      > I've updated the test description to be in sync with the WSDL for
                                      > complex-rpc-encoded.
                                      >
                                      > Re: simple-rpc-encoded, SimpleFault1 needs to be thrown when
                                      > "whichFault" is 1 or not 2 and SimpleFault2 when "whichFault" is 2. This
                                      > was also mentioned in the document. Do you want me to clarify it any
                                      > further ?
                                      >
                                      > Thanks,
                                      > -Arun
                                      >
                                      > Bob Cunnings wrote:
                                      >
                                      > > Re: complex-rpc-encoded
                                      > >
                                      > > There is a discrepency between the prose specification and the WSDL
                                      > > definitions for operations "echoMultipleFaults1" and
                                      > > "echoMultipleFaults2".
                                      > > I am proceeding on the assumption that the WSDL is correct and that
                                      > > control
                                      > > parameter "1" results in ComplexFault1, and so on.
                                      > >
                                      > > RC
                                      > >
                                      > > > I've updated the WSDLs and the test specifications at
                                      > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                                      > > >
                                      > > > I've restructured some of the tests and removed a not-so-realistic use
                                      > > > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                                      > > > further clarification.
                                      > > >
                                      > > > Have a nice weekend!
                                      > > > -Arun
                                      > > >
                                      > > > Bob Cunnings wrote:
                                      > > >
                                      > > > > I think it's a good idea, it would be easy to do. In the case of
                                      > > arrays
                                      > > > > how about having the input message specify the number of items in
                                      > > > > the returned array as well as the value to be used for the items?
                                      > > > > (one value would be repeated n times) Otherwise the array size will
                                      > > > > have to be fixed in the spec or left to the whim of the receiver.This
                                      > > > > expands the size of the input messages, e.g.
                                      > > > > "echoExtendedStructFault" would require 6 input params, one for
                                      > > > > the size and 5 to define the struct members. However, like you
                                      > > > > say, it's always satisfying to see the request data echoed in the
                                      > > > > reponse for validation purposes.
                                      > > > >
                                      > > > > RC
                                      > > > >
                                      > > > > > All simple-rpc-encoded tests pass. All complex-rpc-encoded envelopes
                                      > > > > > look fine on the first glance. I'll be doing a detailed analysis
                                      > > later.
                                      > > > > >
                                      > > > > > Do you think it makes sense to have an input parameter that can be
                                      > > used
                                      > > > > > to populate the fault detail element ? For instance, if it's a
                                      > > > > > StringFault, then echoStringFault will have the method operation as
                                      > > > > > echoStringFault(String param) and then "param" is used in the detail
                                      > > > > > element of fault. That way I know what exactly I'm expecting in the
                                      > > > > > fault detail.
                                      > > > > >
                                      > > > > > This will need another update to your endpoints but will
                                      > > validate the
                                      > > > > > data contained within the fault. What do you say ?
                                      > > > > >
                                      > > > > > Thanks,
                                      > > > > > -Arun
                                      > > > > >
                                      > > > > > Bob Cunnings wrote:
                                      > > > > >
                                      > > > > > > Looks fine, I've updated the WM endpoints to comply.
                                      > > > > > >
                                      > > > > > > Thanks,
                                      > > > > > >
                                      > > > > > > RC
                                      > > > > > >
                                      > > > > > > > In this particular case yes, it should be an empty fault.
                                      > > However
                                      > > in
                                      > > > > > > > other cases where there an EmptyFault is not thrown, there
                                      > > will be
                                      > > a
                                      > > > > > > > different default behavior. I've updated the specifications at
                                      > > > > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                                      > > > > me know
                                      > > > > > > > if it looks fine.
                                      > > > > > > >
                                      > > > > > > > Thanks,
                                      > > > > > > > -Arun
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > > Bob Cunnings wrote:
                                      > > > > > > >
                                      > > > > > > > > I like your second option, which I understand to mean that out
                                      > > of
                                      > > > > > > > > range input values result in an empty fault. Is that correct?
                                      > > > > If so,
                                      > > > > > > > > what fault code shall be used in those cases?
                                      > > > > > > > >
                                      > > > > > > > > RC
                                      > > > > > > > >
                                      > > > > > > > > > I'll update the test specification to mention that
                                      > > > > env:Server is the
                                      > > > > > > > > > expected fault code in all the faults.
                                      > > > > > > > > >
                                      > > > > > > > > > It's a good idea to define a new fault message. But can we
                                      > > > > construct
                                      > > > > > > > > > this fault such that this also tests another aspect of fault
                                      > > > > > > interop.
                                      > > > > > > > > > Another option we can change the test spec such that:
                                      > > > > > > > > >
                                      > > > > > > > > > Throws empty fault when the parameter = 1 or not 2 or not 3.
                                      > > > > > > > > > Throws fault with a xsd:string member when the parameter
                                      > > = 2.
                                      > > > > > > > > > Throws fault with a xsd:float[] member when the
                                      > > parameter = 3.
                                      > > > > > > > > >
                                      > > > > > > > > > Thus there is a default behavior for each method and there
                                      > > > > is out of
                                      > > > > > > > > > range input parameter. Let me know which one you prefer ?
                                      > > > > > > > > >
                                      > > > > > > > > > Regards,
                                      > > > > > > > > > -Arun
                                      > > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > > > Yahoo! Groups Sponsor
                                      > > > > > > > > ADVERTISEMENT
                                      > > > > > > > > <
                                      > > > > > >
                                      > > > >
                                      > > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=170570101
                                      > >
                                      > > 4:HM/A=1189560/R=0
                                      > > > >
                                      > > > >
                                      > > > > > >
                                      > > > > > > /* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                                      > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > >
                                      > > > -----------------------------------------------------------------
                                      > > > > > > > > This group is a forum for builders of SOAP implementations to
                                      > > > > discuss
                                      > > > > > > > > implementation and interoperability issues. Please stay
                                      > > on-topic.
                                      > > > > > > > >
                                      > > > > > > > > To unsubscribe from this group, send an email to:
                                      > > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > > >
                                      > > > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                      > > > > Service
                                      > > > > > > > > < http://docs.yahoo.com/info/terms/ > .
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > > --
                                      > > > > > > > =============================================
                                      > > > > > > > There is only one me, I must live myself!
                                      > > > > > > > There is only one today, I must live itself!
                                      > > > > > > > =============================================
                                      > > > > > > > http://members.tripod.com/~apgupta/index.html
                                      > > <http://members.tripod.com/%7Eapgupta/index.html>
                                      > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                      > > > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                      > > > > > > > =============================================
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > >
                                      > > -----------------------------------------------------------------
                                      > > > > > > > This group is a forum for builders of SOAP implementations to
                                      > > > > > > discuss implementation and interope
                                      > > > > > > rability issues. Please stay on-topic.
                                      > > > > > > >
                                      > > > > > > > To unsubscribe from this group, send an email to:
                                      > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > > > Your use of Yahoo! Groups is subject to
                                      > > > > > > http://docs.yahoo.com/info/terms/
                                      > > > > > > >
                                      > > > > > > >
                                      > > > > > >
                                      > > > > > >
                                      > > > > > >
                                      > > > > > > Yahoo! Groups Sponsor
                                      > > > > > > ADVERTISEMENT
                                      > > > > > > <
                                      > > > >
                                      > > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                                      > > > > > > <
                                      > > > >
                                      > > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                      > >
                                      > > 4:HM/A=810327/R=0/
                                      > > > >
                                      > > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                      > > > > > >
                                      > > > > > > <
                                      > > > >
                                      > > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                                      > > > > > > <
                                      > > > >
                                      > > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                      > >
                                      > > 4:HM/A=810327/R=1/
                                      > > > >
                                      > > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                      > > > > > >
                                      > > > > > >
                                      > > > > > >
                                      > > > > > > -----------------------------------------------------------------
                                      > > > > > > This group is a forum for builders of SOAP implementations to
                                      > > discuss
                                      > > > > > > implementation and interoperability issues. Please stay on-topic.
                                      > > > > > >
                                      > > > > > > To unsubscribe from this group, send an email to:
                                      > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > > > > >
                                      > > > > > >
                                      > > > > > >
                                      > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                      > > Service
                                      > > > > > > <http://docs.yahoo.com/info/terms/ > .
                                      > > > > >
                                      > > > > >
                                      > > > > > --
                                      > > > > > =============================================
                                      > > > > > There is only one me, I must live myself!
                                      > > > > > There is only one today, I must live itself!
                                      > > > > > =============================================
                                      > > > > > http://members.tripod.com/~apgupta/index.html
                                      > > <http://members.tripod.com/%7Eapgupta/index.html>
                                      > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                      > > > > > =============================================
                                      > > > > >
                                      > > > > >
                                      > > > > >
                                      > > > > >
                                      > > > > > -----------------------------------------------------------------
                                      > > > > > This group is a forum for builders of SOAP implementations to
                                      > > > > discuss implementation and interope
                                      > > > > rability issues. Please stay on-topic.
                                      > > > > >
                                      > > > > > To unsubscribe from this group, send an email to:
                                      > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > > > >
                                      > > > > >
                                      > > > > >
                                      > > > > > Your use of Yahoo! Groups is subject to
                                      > > > > http://docs.yahoo.com/info/terms/
                                      > > > > >
                                      > > > > >
                                      > > > >
                                      > > > >
                                      > > > >
                                      > > > > Yahoo! Groups Sponsor
                                      > > > > ADVERTISEMENT
                                      > > > >
                                      > > <
                                      > > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=17057010
                                      > >
                                      > > 14:HM/A=1189558/R=0/* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/ >
                                      > > > >
                                      > > > >
                                      > > > >
                                      > > > > -----------------------------------------------------------------
                                      > > > > This group is a forum for builders of SOAP implementations to discuss
                                      > > > > implementation and interoperability issues. Please stay on-topic.
                                      > > > >
                                      > > > > To unsubscribe from this group, send an email to:
                                      > > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > > >
                                      > > > >
                                      > > > >
                                      > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                      > > > > <http://docs.yahoo.com/info/terms/ > .
                                      > > >
                                      > > >
                                      > > > --
                                      > > > =============================================
                                      > > > There is only one me, I must live myself!
                                      > > > There is only one today, I must live itself!
                                      > > > =============================================
                                      > > > http://members.tripod.com/~apgupta/index.html
                                      > > <http://members.tripod.com/%7Eapgupta/index.html>
                                      > > > =============================================
                                      > > >
                                      > > >
                                      > > >
                                      > > >
                                      > > > -----------------------------------------------------------------
                                      > > > This group is a forum for builders of SOAP implementations to discuss
                                      > > implementation and interoperability issues. Please stay on-topic.
                                      > > >
                                      > > > To unsubscribe from this group, send an email to:
                                      > > > soapbuilders-unsubscribe@yahoogroups.com
                                      > > >
                                      > > >
                                      > > >
                                      > > > Your use of Yahoo! Groups is subject to
                                      > > http://docs.yahoo.com/info/terms/
                                      > > >
                                      > > >
                                      > >
                                      > >
                                      > >
                                      > >
                                      > > Yahoo! Groups Sponsor
                                      > > ADVERTISEMENT
                                      > > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg>
                                      > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/
                                      *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                      > >
                                      > > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif>
                                      > > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/
                                      *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                      > >
                                      > >
                                      > >
                                      > > -----------------------------------------------------------------
                                      > > This group is a forum for builders of SOAP implementations to discuss
                                      > > implementation and interoperability issues. Please stay on-topic.
                                      > >
                                      > > To unsubscribe from this group, send an email to:
                                      > > soapbuilders-unsubscribe@yahoogroups.com
                                      > >
                                      > >
                                      > >
                                      > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                      > > <http://docs.yahoo.com/info/terms/> .
                                      >
                                      >
                                      > --
                                      > =============================================
                                      > There is only one me, I must live myself!
                                      > There is only one today, I must live itself!
                                      > =============================================
                                      > http://members.tripod.com/~apgupta/index.html
                                      > =============================================
                                      >
                                      >
                                      >
                                      >
                                      > -----------------------------------------------------------------
                                      > This group is a forum for builders of SOAP implementations to discuss implementation and interope
                                      rability issues. Please stay on-topic.
                                      >
                                      > To unsubscribe from this group, send an email to:
                                      > soapbuilders-unsubscribe@yahoogroups.com
                                      >
                                      >
                                      >
                                      > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
                                      >
                                      >
                                    • Arun Gupta
                                      I ve updated the document to clarify this. Couple of issues with WM s endpoint: 1). Faults with array elements are not getting serialized correctly. Here is
                                      Message 18 of 24 , Sep 10, 2002
                                      • 0 Attachment
                                        I've updated the document to clarify this.

                                        Couple of issues with WM's endpoint:

                                        1). Faults with array elements are not getting serialized correctly.
                                        Here is request/repsonse message for StringFault.

                                        Request message
                                        ---------------
                                        <?xml version="1.0" encoding="UTF-8"?>
                                        <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                        xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                        xmlns:ns0="http://soapinterop.org/types"
                                        xmlns:ns1="http://soapinterop.org/wsdl"
                                        env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                        <env:Body>
                                        <ns1:echoMultipleFaults2>
                                        <whichFault xsi:type="xsd:int">3</whichFault>
                                        <param1 xsi:type="xsd:string">Hello SOAPBuilders!</param1>
                                        <param2 xsi:type="xsd:float">2.14748365E9</param2>
                                        <param3 href="#ID1"/>
                                        </ns1:echoMultipleFaults2>
                                        <ns0:ArrayOfString id="ID1" xsi:type="enc:Array"
                                        enc:arrayType="xsd:string[14]">
                                        <item xsi:type="xsd:string">Now</item>
                                        <item xsi:type="xsd:string">is</item>
                                        <item xsi:type="xsd:string">the</item>
                                        <item xsi:type="xsd:string">time</item>
                                        <item xsi:type="xsd:string">for</item>
                                        <item xsi:type="xsd:string">all</item>
                                        <item xsi:type="xsd:string">wise</item>
                                        <item xsi:type="xsd:string">men</item>
                                        <item xsi:type="xsd:string">to</item>
                                        <item xsi:type="xsd:string">raise</item>
                                        <item xsi:type="xsd:string">for</item>
                                        <item xsi:type="xsd:string">the</item>
                                        <item xsi:type="xsd:string">country's</item>
                                        <item xsi:type="xsd:string">help</item>
                                        </ns0:ArrayOfString></env:Body></env:Envelope>

                                        Response message
                                        ----------------
                                        <?xml version="1.0" encoding="UTF-8"?>
                                        <SOAP-ENV:Envelope
                                        xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                        <SOAP-ENV:Body>
                                        <SOAP-ENV:Fault>
                                        <faultcode
                                        xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/">
                                        ns:Server</faultcode>
                                        <faultstring>
                                        Fault in response to 'echoMultipleFaults2'.
                                        </faultstring>
                                        <detail>
                                        <d:part6
                                        SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                        SOAP-ENC:arrayType="nsa:string[0]"
                                        SOAP-ENC:offset="[0]"
                                        xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                                        xmlns:d="http://soapinterop.org/wsdl"
                                        xmlns:nsa="http://www.w3.org/2001/XMLSchema"/>
                                        </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

                                        2). Enums are not getting echoed back correctly. Here are the
                                        request/response messages:

                                        Request message
                                        ---------------
                                        <?xml version="1.0" encoding="UTF-8"?>
                                        <env:Envelope
                                        xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                        xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                        xmlns:ns0="http://soapinterop.org/types"
                                        xmlns:ns1="http://soapinterop.org/wsdl"
                                        env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                        <env:Body>
                                        <ns1:echoMultipleFaults4>
                                        <whichFault xsi:type="xsd:int">2</whichFault>
                                        <param1 xsi:type="xsd:int">23532</param1>
                                        <param2 href="#ID1"/></ns1:echoMultipleFaults4>
                                        <ns0:Enum id="ID1" xsi:type="ns0:Enum">1</ns0:Enum>
                                        </env:Body></env:Envelope>

                                        Response message
                                        ----------------
                                        <?xml version="1.0" encoding="UTF-8"?>
                                        <SOAP-ENV:Envelope
                                        xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                        <SOAP-ENV:Body>
                                        <SOAP-ENV:Fault>
                                        <faultcode xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/"
                                        ns:Server</faultcode>
                                        <faultstring>Fault in response to 'echoMultipleFaults4'.
                                        </faultstring>
                                        <detail><d:part9
                                        SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                        xmlns:d="http://soapinterop.org/wsdl">0</d:part9>
                                        </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

                                        Thanks,
                                        -Arun

                                        Bob Cunnings wrote:

                                        > Yes.
                                        > The input message for "echoMultipleFaults3" contains 2 string
                                        > parameters. The Faults that may result, "SimpleFault1" and
                                        > "SimpleFault2" each refer to a fault message containing a single
                                        > string. The question is, what is the connection between input string
                                        > parameters and the fault messages? Which of the input strings,
                                        > param1 or param2, is expected to be echoed in the fault message
                                        > when "whichFault" is 1 (or not 2), and when "whichFault" is 2?
                                        >
                                        > RC
                                        >
                                        > > I've updated the test description to be in sync with the WSDL for
                                        > > complex-rpc-encoded.
                                        > >
                                        > > Re: simple-rpc-encoded, SimpleFault1 needs to be thrown when
                                        > > "whichFault" is 1 or not 2 and SimpleFault2 when "whichFault" is 2. This
                                        > > was also mentioned in the document. Do you want me to clarify it any
                                        > > further ?
                                        > >
                                        > > Thanks,
                                        > > -Arun
                                        > >
                                        > > Bob Cunnings wrote:
                                        > >
                                        > > > Re: complex-rpc-encoded
                                        > > >
                                        > > > There is a discrepency between the prose specification and the WSDL
                                        > > > definitions for operations "echoMultipleFaults1" and
                                        > > > "echoMultipleFaults2".
                                        > > > I am proceeding on the assumption that the WSDL is correct and that
                                        > > > control
                                        > > > parameter "1" results in ComplexFault1, and so on.
                                        > > >
                                        > > > RC
                                        > > >
                                        > > > > I've updated the WSDLs and the test specifications at
                                        > > > > http://soapinterop.java.sun.com/soapbuilders/r4/index.html.
                                        > > > >
                                        > > > > I've restructured some of the tests and removed a
                                        > not-so-realistic use
                                        > > > > case from complex-rpc-encoded/doc-literal. Let me know if it needs
                                        > > > > further clarification.
                                        > > > >
                                        > > > > Have a nice weekend!
                                        > > > > -Arun
                                        > > > >
                                        > > > > Bob Cunnings wrote:
                                        > > > >
                                        > > > > > I think it's a good idea, it would be easy to do. In the case of
                                        > > > arrays
                                        > > > > > how about having the input message specify the number of items in
                                        > > > > > the returned array as well as the value to be used for the items?
                                        > > > > > (one value would be repeated n times) Otherwise the array size will
                                        > > > > > have to be fixed in the spec or left to the whim of the
                                        > receiver.This
                                        > > > > > expands the size of the input messages, e.g.
                                        > > > > > "echoExtendedStructFault" would require 6 input params, one for
                                        > > > > > the size and 5 to define the struct members. However, like you
                                        > > > > > say, it's always satisfying to see the request data echoed in the
                                        > > > > > reponse for validation purposes.
                                        > > > > >
                                        > > > > > RC
                                        > > > > >
                                        > > > > > > All simple-rpc-encoded tests pass. All complex-rpc-encoded
                                        > envelopes
                                        > > > > > > look fine on the first glance. I'll be doing a detailed analysis
                                        > > > later.
                                        > > > > > >
                                        > > > > > > Do you think it makes sense to have an input parameter that
                                        > can be
                                        > > > used
                                        > > > > > > to populate the fault detail element ? For instance, if it's a
                                        > > > > > > StringFault, then echoStringFault will have the method
                                        > operation as
                                        > > > > > > echoStringFault(String param) and then "param" is used in the
                                        > detail
                                        > > > > > > element of fault. That way I know what exactly I'm expecting
                                        > in the
                                        > > > > > > fault detail.
                                        > > > > > >
                                        > > > > > > This will need another update to your endpoints but will
                                        > > > validate the
                                        > > > > > > data contained within the fault. What do you say ?
                                        > > > > > >
                                        > > > > > > Thanks,
                                        > > > > > > -Arun
                                        > > > > > >
                                        > > > > > > Bob Cunnings wrote:
                                        > > > > > >
                                        > > > > > > > Looks fine, I've updated the WM endpoints to comply.
                                        > > > > > > >
                                        > > > > > > > Thanks,
                                        > > > > > > >
                                        > > > > > > > RC
                                        > > > > > > >
                                        > > > > > > > > In this particular case yes, it should be an empty fault.
                                        > > > However
                                        > > > in
                                        > > > > > > > > other cases where there an EmptyFault is not thrown, there
                                        > > > will be
                                        > > > a
                                        > > > > > > > > different default behavior. I've updated the
                                        > specifications at
                                        > > > > > > > >
                                        > http://soapinterop.java.sun.com/soapbuilders/r4/index.html. Let
                                        > > > > > me know
                                        > > > > > > > > if it looks fine.
                                        > > > > > > > >
                                        > > > > > > > > Thanks,
                                        > > > > > > > > -Arun
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > > Bob Cunnings wrote:
                                        > > > > > > > >
                                        > > > > > > > > > I like your second option, which I understand to mean
                                        > that out
                                        > > > of
                                        > > > > > > > > > range input values result in an empty fault. Is that
                                        > correct?
                                        > > > > > If so,
                                        > > > > > > > > > what fault code shall be used in those cases?
                                        > > > > > > > > >
                                        > > > > > > > > > RC
                                        > > > > > > > > >
                                        > > > > > > > > > > I'll update the test specification to mention that
                                        > > > > > env:Server is the
                                        > > > > > > > > > > expected fault code in all the faults.
                                        > > > > > > > > > >
                                        > > > > > > > > > > It's a good idea to define a new fault message. But
                                        > can we
                                        > > > > > construct
                                        > > > > > > > > > > this fault such that this also tests another aspect
                                        > of fault
                                        > > > > > > > interop.
                                        > > > > > > > > > > Another option we can change the test spec such that:
                                        > > > > > > > > > >
                                        > > > > > > > > > > Throws empty fault when the parameter = 1 or not 2 or
                                        > not 3.
                                        > > > > > > > > > > Throws fault with a xsd:string member when the parameter
                                        > > > = 2.
                                        > > > > > > > > > > Throws fault with a xsd:float[] member when the
                                        > > > parameter = 3.
                                        > > > > > > > > > >
                                        > > > > > > > > > > Thus there is a default behavior for each method and
                                        > there
                                        > > > > > is out of
                                        > > > > > > > > > > range input parameter. Let me know which one you prefer ?
                                        > > > > > > > > > >
                                        > > > > > > > > > > Regards,
                                        > > > > > > > > > > -Arun
                                        > > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > > > Yahoo! Groups Sponsor
                                        > > > > > > > > > ADVERTISEMENT
                                        > > > > > > > > > <
                                        > > > > > > >
                                        > > > > >
                                        > > >
                                        > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=170570101
                                        >
                                        > > >
                                        > > > 4:HM/A=1189560/R=0
                                        > > > > >
                                        > > > > >
                                        > > > > > > >
                                        > > > > > > > /* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/ >
                                        > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > >
                                        > > > > -----------------------------------------------------------------
                                        > > > > > > > > > This group is a forum for builders of SOAP
                                        > implementations to
                                        > > > > > discuss
                                        > > > > > > > > > implementation and interoperability issues. Please stay
                                        > > > on-topic.
                                        > > > > > > > > >
                                        > > > > > > > > > To unsubscribe from this group, send an email to:
                                        > > > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > > >
                                        > > > > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                        > > > > > Service
                                        > > > > > > > > > < http://docs.yahoo.com/info/terms/ > .
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > > --
                                        > > > > > > > > =============================================
                                        > > > > > > > > There is only one me, I must live myself!
                                        > > > > > > > > There is only one today, I must live itself!
                                        > > > > > > > > =============================================
                                        > > > > > > > > http://members.tripod.com/~apgupta/index.html
                                        > > > <http://members.tripod.com/%7Eapgupta/index.html>
                                        > > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                        > > > > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                        > > > > > > > > =============================================
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > -----------------------------------------------------------------
                                        > > > > > > > > This group is a forum for builders of SOAP implementations to
                                        > > > > > > > discuss implementation and interope
                                        > > > > > > > rability issues. Please stay on-topic.
                                        > > > > > > > >
                                        > > > > > > > > To unsubscribe from this group, send an email to:
                                        > > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > > > Your use of Yahoo! Groups is subject to
                                        > > > > > > > http://docs.yahoo.com/info/terms/
                                        > > > > > > > >
                                        > > > > > > > >
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > > Yahoo! Groups Sponsor
                                        > > > > > > > ADVERTISEMENT
                                        > > > > > > > <
                                        > > > > >
                                        > > >
                                        > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg >
                                        > > > > > > > <
                                        > > > > >
                                        > > >
                                        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                        >
                                        > > >
                                        > > > 4:HM/A=810327/R=0/
                                        > > > > >
                                        > > > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                        > > > > > > >
                                        > > > > > > > <
                                        > > > > >
                                        > > >
                                        > http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif >
                                        > > > > > > > <
                                        > > > > >
                                        > > >
                                        > http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=170570101
                                        >
                                        > > >
                                        > > > 4:HM/A=810327/R=1/
                                        > > > > >
                                        > > > > > *http://geocities.yahoo.com/ps/info?.refer=blrecs >
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > >
                                        > -----------------------------------------------------------------
                                        > > > > > > > This group is a forum for builders of SOAP implementations to
                                        > > > discuss
                                        > > > > > > > implementation and interoperability issues. Please stay
                                        > on-topic.
                                        > > > > > > >
                                        > > > > > > > To unsubscribe from this group, send an email to:
                                        > > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > >
                                        > > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
                                        > > > Service
                                        > > > > > > > <http://docs.yahoo.com/info/terms/ > .
                                        > > > > > >
                                        > > > > > >
                                        > > > > > > --
                                        > > > > > > =============================================
                                        > > > > > > There is only one me, I must live myself!
                                        > > > > > > There is only one today, I must live itself!
                                        > > > > > > =============================================
                                        > > > > > > http://members.tripod.com/~apgupta/index.html
                                        > > > <http://members.tripod.com/%7Eapgupta/index.html>
                                        > > > > > < http://members.tripod.com/%7Eapgupta/index.html >
                                        > > > > > > =============================================
                                        > > > > > >
                                        > > > > > >
                                        > > > > > >
                                        > > > > > >
                                        > > > > > > -----------------------------------------------------------------
                                        > > > > > > This group is a forum for builders of SOAP implementations to
                                        > > > > > discuss implementation and interope
                                        > > > > > rability issues. Please stay on-topic.
                                        > > > > > >
                                        > > > > > > To unsubscribe from this group, send an email to:
                                        > > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > > > >
                                        > > > > > >
                                        > > > > > >
                                        > > > > > > Your use of Yahoo! Groups is subject to
                                        > > > > > http://docs.yahoo.com/info/terms/
                                        > > > > > >
                                        > > > > > >
                                        > > > > >
                                        > > > > >
                                        > > > > >
                                        > > > > > Yahoo! Groups Sponsor
                                        > > > > > ADVERTISEMENT
                                        > > > > >
                                        > > > <
                                        > > >
                                        > http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=17057010
                                        > > >
                                        > > > 14:HM/A=1189558/R=0/* http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/9/ >
                                        > > > > >
                                        > > > > >
                                        > > > > >
                                        > > > > > -----------------------------------------------------------------
                                        > > > > > This group is a forum for builders of SOAP implementations to
                                        > discuss
                                        > > > > > implementation and interoperability issues. Please stay on-topic.
                                        > > > > >
                                        > > > > > To unsubscribe from this group, send an email to:
                                        > > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > > >
                                        > > > > >
                                        > > > > >
                                        > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                        > > > > > <http://docs.yahoo.com/info/terms/ > .
                                        > > > >
                                        > > > >
                                        > > > > --
                                        > > > > =============================================
                                        > > > > There is only one me, I must live myself!
                                        > > > > There is only one today, I must live itself!
                                        > > > > =============================================
                                        > > > > http://members.tripod.com/~apgupta/index.html
                                        > > > <http://members.tripod.com/%7Eapgupta/index.html>
                                        > > > > =============================================
                                        > > > >
                                        > > > >
                                        > > > >
                                        > > > >
                                        > > > > -----------------------------------------------------------------
                                        > > > > This group is a forum for builders of SOAP implementations to discuss
                                        > > > implementation and interoperability issues. Please stay on-topic.
                                        > > > >
                                        > > > > To unsubscribe from this group, send an email to:
                                        > > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > > >
                                        > > > >
                                        > > > >
                                        > > > > Your use of Yahoo! Groups is subject to
                                        > > > http://docs.yahoo.com/info/terms/
                                        > > > >
                                        > > > >
                                        > > >
                                        > > >
                                        > > >
                                        > > >
                                        > > > Yahoo! Groups Sponsor
                                        > > > ADVERTISEMENT
                                        > > >
                                        > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_1_01.jpg>
                                        > > >
                                        > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/
                                        > *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                        > > >
                                        > > >
                                        > <http://us.a1.yimg.com/us.yimg.com/a/ya/yahoo_geocities/lrec2b_2_02.gif>
                                        > > >
                                        > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/
                                        > *http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                        > > >
                                        > > >
                                        > > >
                                        > > > -----------------------------------------------------------------
                                        > > > This group is a forum for builders of SOAP implementations to discuss
                                        > > > implementation and interoperability issues. Please stay on-topic.
                                        > > >
                                        > > > To unsubscribe from this group, send an email to:
                                        > > > soapbuilders-unsubscribe@yahoogroups.com
                                        > > >
                                        > > >
                                        > > >
                                        > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                        > > > <http://docs.yahoo.com/info/terms/> .
                                        > >
                                        > >
                                        > > --
                                        > > =============================================
                                        > > There is only one me, I must live myself!
                                        > > There is only one today, I must live itself!
                                        > > =============================================
                                        > > http://members.tripod.com/~apgupta/index.html
                                        > > =============================================
                                        > >
                                        > >
                                        > >
                                        > >
                                        > > -----------------------------------------------------------------
                                        > > This group is a forum for builders of SOAP implementations to discuss
                                        > implementation and interope
                                        > rability issues. Please stay on-topic.
                                        > >
                                        > > To unsubscribe from this group, send an email to:
                                        > > soapbuilders-unsubscribe@yahoogroups.com
                                        > >
                                        > >
                                        > >
                                        > > Your use of Yahoo! Groups is subject to
                                        > http://docs.yahoo.com/info/terms/
                                        > >
                                        > >
                                        >
                                        >
                                        >
                                        > Yahoo! Groups Sponsor
                                        > ADVERTISEMENT
                                        > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=0/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                        > <http://rd.yahoo.com/M=212804.2303158.3720906.2225242/D=egroupweb/S=1705701014:HM/A=810327/R=1/*http://geocities.yahoo.com/ps/info?.refer=blrecs>
                                        >
                                        >
                                        >
                                        > -----------------------------------------------------------------
                                        > This group is a forum for builders of SOAP implementations to discuss
                                        > implementation and interoperability issues. Please stay on-topic.
                                        >
                                        > To unsubscribe from this group, send an email to:
                                        > soapbuilders-unsubscribe@yahoogroups.com
                                        >
                                        >
                                        >
                                        > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                        > <http://docs.yahoo.com/info/terms/>.


                                        --
                                        =============================================
                                        There is only one me, I must live myself!
                                        There is only one today, I must live itself!
                                        =============================================
                                        http://members.tripod.com/~apgupta/index.html
                                        =============================================
                                      • Bob Cunnings
                                        Arun, Ok, it looks like the service is falling down on the id/href resolution, I ll get this fixed. Thanks! RC
                                        Message 19 of 24 , Sep 10, 2002
                                        • 0 Attachment
                                          Arun,

                                          Ok, it looks like the service is falling down on the id/href resolution,
                                          I'll get this fixed.

                                          Thanks!

                                          RC

                                          > I've updated the document to clarify this.
                                          >
                                          > Couple of issues with WM's endpoint:
                                          >
                                          > 1). Faults with array elements are not getting serialized correctly.
                                          > Here is request/repsonse message for StringFault.
                                          >
                                          > Request message
                                          > ---------------
                                          > <?xml version="1.0" encoding="UTF-8"?>
                                          > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                          > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                          > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                          > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                          > xmlns:ns0="http://soapinterop.org/types"
                                          > xmlns:ns1="http://soapinterop.org/wsdl"
                                          > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                          > <env:Body>
                                          > <ns1:echoMultipleFaults2>
                                          > <whichFault xsi:type="xsd:int">3</whichFault>
                                          > <param1 xsi:type="xsd:string">Hello SOAPBuilders!</param1>
                                          > <param2 xsi:type="xsd:float">2.14748365E9</param2>
                                          > <param3 href="#ID1"/>
                                          > </ns1:echoMultipleFaults2>
                                          > <ns0:ArrayOfString id="ID1" xsi:type="enc:Array"
                                          > enc:arrayType="xsd:string[14]">
                                          > <item xsi:type="xsd:string">Now</item>
                                          > <item xsi:type="xsd:string">is</item>
                                          > <item xsi:type="xsd:string">the</item>
                                          > <item xsi:type="xsd:string">time</item>
                                          > <item xsi:type="xsd:string">for</item>
                                          > <item xsi:type="xsd:string">all</item>
                                          > <item xsi:type="xsd:string">wise</item>
                                          > <item xsi:type="xsd:string">men</item>
                                          > <item xsi:type="xsd:string">to</item>
                                          > <item xsi:type="xsd:string">raise</item>
                                          > <item xsi:type="xsd:string">for</item>
                                          > <item xsi:type="xsd:string">the</item>
                                          > <item xsi:type="xsd:string">country's</item>
                                          > <item xsi:type="xsd:string">help</item>
                                          > </ns0:ArrayOfString></env:Body></env:Envelope>
                                          >
                                          > Response message
                                          > ----------------
                                          > <?xml version="1.0" encoding="UTF-8"?>
                                          > <SOAP-ENV:Envelope
                                          > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                          > <SOAP-ENV:Body>
                                          > <SOAP-ENV:Fault>
                                          > <faultcode
                                          > xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/">
                                          > ns:Server</faultcode>
                                          > <faultstring>
                                          > Fault in response to 'echoMultipleFaults2'.
                                          > </faultstring>
                                          > <detail>
                                          > <d:part6
                                          > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                          > SOAP-ENC:arrayType="nsa:string[0]"
                                          > SOAP-ENC:offset="[0]"
                                          > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                                          > xmlns:d="http://soapinterop.org/wsdl"
                                          > xmlns:nsa="http://www.w3.org/2001/XMLSchema"/>
                                          > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                          >
                                          > 2). Enums are not getting echoed back correctly. Here are the
                                          > request/response messages:
                                          >
                                          > Request message
                                          > ---------------
                                          > <?xml version="1.0" encoding="UTF-8"?>
                                          > <env:Envelope
                                          > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                          > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                          > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                          > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                          > xmlns:ns0="http://soapinterop.org/types"
                                          > xmlns:ns1="http://soapinterop.org/wsdl"
                                          > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                          > <env:Body>
                                          > <ns1:echoMultipleFaults4>
                                          > <whichFault xsi:type="xsd:int">2</whichFault>
                                          > <param1 xsi:type="xsd:int">23532</param1>
                                          > <param2 href="#ID1"/></ns1:echoMultipleFaults4>
                                          > <ns0:Enum id="ID1" xsi:type="ns0:Enum">1</ns0:Enum>
                                          > </env:Body></env:Envelope>
                                          >
                                          > Response message
                                          > ----------------
                                          > <?xml version="1.0" encoding="UTF-8"?>
                                          > <SOAP-ENV:Envelope
                                          > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                          > <SOAP-ENV:Body>
                                          > <SOAP-ENV:Fault>
                                          > <faultcode xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/"
                                          > ns:Server</faultcode>
                                          > <faultstring>Fault in response to 'echoMultipleFaults4'.
                                          > </faultstring>
                                          > <detail><d:part9
                                          > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                          > xmlns:d="http://soapinterop.org/wsdl">0</d:part9>
                                          > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                          >
                                          > Thanks,
                                          > -Arun
                                          >
                                        • Bob Cunnings
                                          Hi, The id/href problems are fixed now. Thanks for the report, RC
                                          Message 20 of 24 , Sep 10, 2002
                                          • 0 Attachment
                                            Hi,

                                            The id/href problems are fixed now.

                                            Thanks for the report,

                                            RC

                                            > I've updated the document to clarify this.
                                            >
                                            > Couple of issues with WM's endpoint:
                                            >
                                            > 1). Faults with array elements are not getting serialized correctly.
                                            > Here is request/repsonse message for StringFault.
                                            >
                                            > Request message
                                            > ---------------
                                            > <?xml version="1.0" encoding="UTF-8"?>
                                            > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                            > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                            > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                            > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                            > xmlns:ns0="http://soapinterop.org/types"
                                            > xmlns:ns1="http://soapinterop.org/wsdl"
                                            > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                            > <env:Body>
                                            > <ns1:echoMultipleFaults2>
                                            > <whichFault xsi:type="xsd:int">3</whichFault>
                                            > <param1 xsi:type="xsd:string">Hello SOAPBuilders!</param1>
                                            > <param2 xsi:type="xsd:float">2.14748365E9</param2>
                                            > <param3 href="#ID1"/>
                                            > </ns1:echoMultipleFaults2>
                                            > <ns0:ArrayOfString id="ID1" xsi:type="enc:Array"
                                            > enc:arrayType="xsd:string[14]">
                                            > <item xsi:type="xsd:string">Now</item>
                                            > <item xsi:type="xsd:string">is</item>
                                            > <item xsi:type="xsd:string">the</item>
                                            > <item xsi:type="xsd:string">time</item>
                                            > <item xsi:type="xsd:string">for</item>
                                            > <item xsi:type="xsd:string">all</item>
                                            > <item xsi:type="xsd:string">wise</item>
                                            > <item xsi:type="xsd:string">men</item>
                                            > <item xsi:type="xsd:string">to</item>
                                            > <item xsi:type="xsd:string">raise</item>
                                            > <item xsi:type="xsd:string">for</item>
                                            > <item xsi:type="xsd:string">the</item>
                                            > <item xsi:type="xsd:string">country's</item>
                                            > <item xsi:type="xsd:string">help</item>
                                            > </ns0:ArrayOfString></env:Body></env:Envelope>
                                            >
                                            > Response message
                                            > ----------------
                                            > <?xml version="1.0" encoding="UTF-8"?>
                                            > <SOAP-ENV:Envelope
                                            > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                            > <SOAP-ENV:Body>
                                            > <SOAP-ENV:Fault>
                                            > <faultcode
                                            > xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/">
                                            > ns:Server</faultcode>
                                            > <faultstring>
                                            > Fault in response to 'echoMultipleFaults2'.
                                            > </faultstring>
                                            > <detail>
                                            > <d:part6
                                            > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                            > SOAP-ENC:arrayType="nsa:string[0]"
                                            > SOAP-ENC:offset="[0]"
                                            > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                                            > xmlns:d="http://soapinterop.org/wsdl"
                                            > xmlns:nsa="http://www.w3.org/2001/XMLSchema"/>
                                            > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                            >
                                            > 2). Enums are not getting echoed back correctly. Here are the
                                            > request/response messages:
                                            >
                                            > Request message
                                            > ---------------
                                            > <?xml version="1.0" encoding="UTF-8"?>
                                            > <env:Envelope
                                            > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                            > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                            > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                            > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                            > xmlns:ns0="http://soapinterop.org/types"
                                            > xmlns:ns1="http://soapinterop.org/wsdl"
                                            > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                            > <env:Body>
                                            > <ns1:echoMultipleFaults4>
                                            > <whichFault xsi:type="xsd:int">2</whichFault>
                                            > <param1 xsi:type="xsd:int">23532</param1>
                                            > <param2 href="#ID1"/></ns1:echoMultipleFaults4>
                                            > <ns0:Enum id="ID1" xsi:type="ns0:Enum">1</ns0:Enum>
                                            > </env:Body></env:Envelope>
                                            >
                                            > Response message
                                            > ----------------
                                            > <?xml version="1.0" encoding="UTF-8"?>
                                            > <SOAP-ENV:Envelope
                                            > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                            > <SOAP-ENV:Body>
                                            > <SOAP-ENV:Fault>
                                            > <faultcode xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/"
                                            > ns:Server</faultcode>
                                            > <faultstring>Fault in response to 'echoMultipleFaults4'.
                                            > </faultstring>
                                            > <detail><d:part9
                                            > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                            > xmlns:d="http://soapinterop.org/wsdl">0</d:part9>
                                            > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                            >
                                            > Thanks,
                                            > -Arun
                                            >
                                          • Arun Gupta
                                            I ran Sun client on WM simple-rpc-encoded endpoint. All tests pass. Thanks, -Arun ... -- ============================================= There is only one me, I
                                            Message 21 of 24 , Sep 11, 2002
                                            • 0 Attachment
                                              I ran Sun client on WM simple-rpc-encoded endpoint. All tests pass.

                                              Thanks,
                                              -Arun

                                              Bob Cunnings wrote:

                                              > Hi,
                                              >
                                              > The id/href problems are fixed now.
                                              >
                                              > Thanks for the report,
                                              >
                                              > RC
                                              >
                                              > > I've updated the document to clarify this.
                                              > >
                                              > > Couple of issues with WM's endpoint:
                                              > >
                                              > > 1). Faults with array elements are not getting serialized correctly.
                                              > > Here is request/repsonse message for StringFault.
                                              > >
                                              > > Request message
                                              > > ---------------
                                              > > <?xml version="1.0" encoding="UTF-8"?>
                                              > > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                              > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                              > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                              > > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                              > > xmlns:ns0="http://soapinterop.org/types"
                                              > > xmlns:ns1="http://soapinterop.org/wsdl"
                                              > > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                              > > <env:Body>
                                              > > <ns1:echoMultipleFaults2>
                                              > > <whichFault xsi:type="xsd:int">3</whichFault>
                                              > > <param1 xsi:type="xsd:string">Hello SOAPBuilders!</param1>
                                              > > <param2 xsi:type="xsd:float">2.14748365E9</param2>
                                              > > <param3 href="#ID1"/>
                                              > > </ns1:echoMultipleFaults2>
                                              > > <ns0:ArrayOfString id="ID1" xsi:type="enc:Array"
                                              > > enc:arrayType="xsd:string[14]">
                                              > > <item xsi:type="xsd:string">Now</item>
                                              > > <item xsi:type="xsd:string">is</item>
                                              > > <item xsi:type="xsd:string">the</item>
                                              > > <item xsi:type="xsd:string">time</item>
                                              > > <item xsi:type="xsd:string">for</item>
                                              > > <item xsi:type="xsd:string">all</item>
                                              > > <item xsi:type="xsd:string">wise</item>
                                              > > <item xsi:type="xsd:string">men</item>
                                              > > <item xsi:type="xsd:string">to</item>
                                              > > <item xsi:type="xsd:string">raise</item>
                                              > > <item xsi:type="xsd:string">for</item>
                                              > > <item xsi:type="xsd:string">the</item>
                                              > > <item xsi:type="xsd:string">country's</item>
                                              > > <item xsi:type="xsd:string">help</item>
                                              > > </ns0:ArrayOfString></env:Body></env:Envelope>
                                              > >
                                              > > Response message
                                              > > ----------------
                                              > > <?xml version="1.0" encoding="UTF-8"?>
                                              > > <SOAP-ENV:Envelope
                                              > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                              > > <SOAP-ENV:Body>
                                              > > <SOAP-ENV:Fault>
                                              > > <faultcode
                                              > > xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/">
                                              > > ns:Server</faultcode>
                                              > > <faultstring>
                                              > > Fault in response to 'echoMultipleFaults2'.
                                              > > </faultstring>
                                              > > <detail>
                                              > > <d:part6
                                              > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                              > > SOAP-ENC:arrayType="nsa:string[0]"
                                              > > SOAP-ENC:offset="[0]"
                                              > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                                              > > xmlns:d="http://soapinterop.org/wsdl"
                                              > > xmlns:nsa="http://www.w3.org/2001/XMLSchema"/>
                                              > > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                              > >
                                              > > 2). Enums are not getting echoed back correctly. Here are the
                                              > > request/response messages:
                                              > >
                                              > > Request message
                                              > > ---------------
                                              > > <?xml version="1.0" encoding="UTF-8"?>
                                              > > <env:Envelope
                                              > > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                                              > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                                              > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                              > > xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                                              > > xmlns:ns0="http://soapinterop.org/types"
                                              > > xmlns:ns1="http://soapinterop.org/wsdl"
                                              > > env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                                              > > <env:Body>
                                              > > <ns1:echoMultipleFaults4>
                                              > > <whichFault xsi:type="xsd:int">2</whichFault>
                                              > > <param1 xsi:type="xsd:int">23532</param1>
                                              > > <param2 href="#ID1"/></ns1:echoMultipleFaults4>
                                              > > <ns0:Enum id="ID1" xsi:type="ns0:Enum">1</ns0:Enum>
                                              > > </env:Body></env:Envelope>
                                              > >
                                              > > Response message
                                              > > ----------------
                                              > > <?xml version="1.0" encoding="UTF-8"?>
                                              > > <SOAP-ENV:Envelope
                                              > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
                                              > > <SOAP-ENV:Body>
                                              > > <SOAP-ENV:Fault>
                                              > > <faultcode xmlns:ns="http://schemas.xmlsoap.org/soap/envelope/"
                                              > > ns:Server</faultcode>
                                              > > <faultstring>Fault in response to 'echoMultipleFaults4'.
                                              > > </faultstring>
                                              > > <detail><d:part9
                                              > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                                              > > xmlns:d="http://soapinterop.org/wsdl">0</d:part9>
                                              > > </detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
                                              > >
                                              > > Thanks,
                                              > > -Arun
                                              > >
                                              >
                                              >
                                              >
                                              >
                                              >
                                              > Yahoo! Groups Sponsor
                                              > ADVERTISEMENT
                                              > <http://rd.yahoo.com/M=229441.2336363.3766536.2225242/D=egroupweb/S=1705701014:HM/A=1189560/R=0/*http://www.bmgmusic.com/acq/ee/q6/enroll/mhn/10/>
                                              >
                                              >
                                              > -----------------------------------------------------------------
                                              > This group is a forum for builders of SOAP implementations to discuss
                                              > implementation and interoperability issues. Please stay on-topic.
                                              >
                                              > To unsubscribe from this group, send an email to:
                                              > soapbuilders-unsubscribe@yahoogroups.com
                                              >
                                              >
                                              >
                                              > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
                                              > <http://docs.yahoo.com/info/terms/>.


                                              --
                                              =============================================
                                              There is only one me, I must live myself!
                                              There is only one today, I must live itself!
                                              =============================================
                                              http://members.tripod.com/~apgupta/index.html
                                              =============================================
                                            Your message has been successfully submitted and would be delivered to recipients shortly.