Re: message id interoperability issue with .net 2.0

Hi, Uthaiyashankar [EMAIL PROTECTED] writes: .NET 2.0 client expects urn:uuid prefix in the message id. (i.e wsa:MessageIDurn: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? +1 ,

Re: message id interoperability issue with .net 2.0

Dinesh Premalal wrote: Hi, Uthaiyashankar [EMAIL PROTECTED] writes: .NET 2.0 client expects urn:uuid prefix in the message id. (i.e wsa:MessageIDurn: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

Re: message id interoperability issue with .net 2.0

Manjula Peiris wrote: 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:MessageID6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID). When using with .NET 3.0 clients, above message id works without any

message id interoperability issue with .net 2.0

Hi, Axis2/C creates wsa:MessageID as a sequence of characters. (E.g: wsa:MessageID6b85e6c2-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

Re: message id interoperability issue with .net 2.0

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:MessageID6b85e6c2-4645-1dd1-2636-000c292fec05/wsa:MessageID). When using with .NET 3.0 clients, above message id works without any problem. However, when

Re: message id interoperability issue with .net 2.0

As I saw in the ws-addressing spec they have also used uuid as prefix in the sample messages. +1 for this If this will not break any existing code scenarios. Thanks Milinda On Fri, Jul 4, 2008 at 4:12 PM, Manjula Peiris [EMAIL PROTECTED] wrote: On Fri, 2008-07-04 at 15:58 +0530,