RE: Dispatching GuaranteedFault (MessageTest-1G)

"Jonathan Marsh" <[email protected]>
Newsgroups gmane.comp.web.services.description
Message-ID <003c01c739fb$915cefb0$d901640a@DELLICIOUS>
I've done this, as follows:

 

1)      Removed GenericSOAPBinding from MessageTest-1G, including the
endpoint referring to it.

2)      Created MessageTest-6G that only has the GenericSOAPBinding,
including removing endpoints associated with other bindings.

3)      Changed the content models of Send and GuaranteedFault to elements
sendString and sendInt, with xs:string and xs:int types repectively.

4)      Changed the name of the Service, changed some comments

 

That's about it.  Hopefully the bogus red resulting from this surgery will
evaporate quickly.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

  _____  

From: [email protected] [mailto:[email protected]] On
Behalf Of Jonathan Marsh
Sent: Wednesday, January 10, 2007 11:27 AM
To: 'www-ws-desc'
Subject: Dispatching GuaranteedFault (MessageTest-1G)

 

There is an unfortunate interaction in MessageTest-1G, with the
GuaranteedFault and Send operations when bound to the GenericSOAPBinding.

 

These operations test the #any and #none content models.  Since the payload
can be any XML, or no XML, and there are no per-operation details specified,
these messages can't be property dispatched by Axis2.  The mechanisms we
typically use (wsa:Action, {soap action}, or unique GEDs, {http location})
aren't available.

 

The problem arises in that the test tries to simultaneously stress test
constructs like #any, #none, and generic bindings.  Testing these features
in isolation prevents the unfortunate interaction.

 

To solve this, I propose we untease these parts of the test, in the
following way:

 

1)  Remove the GenericSOAPBinding from MessageTest-1G.

2)  Create a new test GenericBinding-1G which binds the interesting types of
operations:

a.   in-out MEP

b.   in-out MEP with returned fault

c.   in-only MEP

d.   robust-in-only MEP

e.   robust-in-only MEP with returned fault.

 

I'm happy to do this work if the implementers agree it's useful.  Let's
discuss on Thursday.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.