Dinesh Premalal wrote:
Hi,
Uthaiyashankar <[EMAIL PROTECTED]> writes:
.NET 2.0 client expects "urn:uuid" prefix in the message id. (i.e
urn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05
). To be able to interoperate with .NET 2.0 it is better to add
"urn:uuid" prefix to message id. WDYT?
Hi,
Uthaiyashankar <[EMAIL PROTECTED]> writes:
> .NET 2.0 client expects "urn:uuid" prefix in the message id. (i.e
> urn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05
> ). To be able to interoperate with .NET 2.0 it is better to add
> "urn:uuid" prefix to message id. WDYT?
+1 , after adding urn:uuid
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:
6b85e6c2-4645-1dd1-2636-000c292fec05).
When using with .NET 3.0 clients, above message id works without any
problem. However, when using wi
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, Uthaiyasha
On Fri, 2008-07-04 at 15:58 +0530, Uthaiyashankar wrote:
> Hi,
>
> Axis2/C creates wsa:MessageID as a sequence of characters. (E.g:
> 6b85e6c2-4645-1dd1-2636-000c292fec05).
> When using with .NET 3.0 clients, above message id works without any
> problem. However, when using with .NET 2.0 cli
Hi,
Axis2/C creates wsa:MessageID as a sequence of characters. (E.g:
6b85e6c2-4645-1dd1-2636-000c292fec05).
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
