Hi Deepal,
I checked the test and yes i was able to run it successfull.
anyway, when i try to put this in my running enviroment i get this strange
error:
[java] Exception in thread "main" org.apache.axis2.AxisFault: Unable to
fin
d corresponding context for the serviceGroupId:
urn:uuid:97198317A8B28D4CDF11775
98325288
In services.xml on the server side i have the
scope="soapsession" attribute
At the client side I have the following code
*options.setManageSession(true); *
*...*
client.engageModule(new QName("addressing"));
Is there anything else to configure?
Thanks,
Nencho
2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
Hi Nencho ,
Axis2 soap session to be work , you need to engage addressing in both
the side.
It is working , there is a test case in the build so we are testing that
daily.
org.apache.axis2.engine.ServiceGroupContextTest
Thanks
Deepal
> Hi All,
>
> I read this axis2 session management article:
> http://www.developer.com/java/web/article.php/3620661
>
> Basically, it says that i can define my services being of a soap
> session scope,
> then i have to put this option on my client:
> *options.setManageSession(true);*
>
> Therefore it is expected for the service to include
> <wsa:ReferenceParameters>
> element as an session identifier in the soap envelope.
>
> I tested this and it does not work - axis2 does not put that element,
> in order
> to be used as session identifier.Am i missing something or this is a
bug?
>
> Thanks,
> Nencho
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
