Usage of EDXL-DE with SOAP - Unique Wire Signatures

["Mark Carlson - Conneva, Inc." <conneva@gmail.com>]

The interface we are building will expose selected ROSS functionality using a web services interface.  One of our design goals is to follow the best practice guidelines of the 
WS-I Basic Profile 1.0.  The "Wire Signatures for Operations" guideline requires each web services operation to have a unique "on the wire" signature.  In other words, multiple operations can not have the qualified name in the SOAP body.

I suspect the underlying reason for this is to avoid duplicate class issues when the proxy code is generated to invoke a particular service.  Identical on the wire signatures would result in duplicate classes in the generated proxy code.

SOAP messages containing only an EDXL-DE element in the message body could certainly be used in many ways (carrying RM messages, for one).  However, unless those messages were "wrapped" in some other element to distinguish the operation's on the wire signature, we could expect issues with generated proxy code and could not claim WS-I Basic Profile conformance.  Another workaround would bedefining a single "processEDXLMessage" operation which calls other
services based on the content of the message.

Are any of you using EDXL with SOAP?  If so, how have you addressed this issue?  

Mark Carlson