axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manjula Peiris <manj...@wso2.com>
Subject Re: message id interoperability issue with .net 2.0
Date Fri, 04 Jul 2008 10:42:44 GMT

On Fri, 2008-07-04 at 15:58 +0530, Uthaiyashankar wrote:
> Hi,
> 
> Axis2/C creates wsa:MessageID as a sequence of characters. (E.g:  
> <wsa:MessageID>6b85e6c2-4645-1dd1-2636-000c292fec05</wsa:MessageID>).  
> When using with .NET 3.0 clients, above message id works without any 
> problem. However, when using with .NET 2.0 clients, this message id 
> could not be processed by .NET client.
> 
> .NET 2.0 client expects "urn:uuid" prefix in the message id.  (i.e 
> <wsa:MessageID>urn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05</wsa:MessageID>

> ). To be able to interoperate with .NET 2.0 it is better to add 
> "urn:uuid" prefix to message id. WDYT?

Actually according to the WS-Addressing spec [1] MessageID should be an
opaque uri. According to [2] the part before ":" is optional. So what
Axis2/C sends is correct. But adding urn:uuid: will not break other
interoperable scenarios. So I am +1 for adding urn:uid.

[1] http://www.w3.org/Submission/ws-addressing/#_Toc77464322
 
[2] http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html

-Manjula.

> 
> Regards,
> Shankar
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message