Hi Deepal, what about this jira issue:
https://issues.apache.org/jira/browse/AXIS2-2561 Does it means that we need to wait the issue to be closed in order to use the soap session scope? 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]
