Hi All,

we have some webservices which can be consumed without problem by a .NET
client.

We have only a problems with a webservice which is defined a
session=SOAPSession.

Appareantly when a servicegroupid is generated and send back it is not
picked-up by the .NET client.

I thought Axis2 webservices were interoperable with .NET ?

Is WS-adrressing not the same for Axis2 and .NET

What can we do about it (or the .NET client) ?

Has anyone have succesfull experience with .NET client and a webservice with
SOAPSession ?

Some .NET code snippets, articels , more info that could help us ?

Regards,

H.

Reply via email to