Re: [axis2 ]soap session scope does not work

Hi Paul, Do you know if with the Secure conversation i can force the client to send the username token only the first time without having the login operation, or I still need this entry point? Is there any usefull documentation on the rampart secure conv. implementation? Thanks, Nencho

Re: [axis2 ]soap session scope does not work

Nencho Yes, the conversation initiation will happen on the first call - no matter what operation. I think there are good samples in Rampart. They are the best approach to getting started with Rampart. Paul On 5/2/07, Nencho Lupanov [EMAIL PROTECTED] wrote: Hi Paul, Do you know if with the

Re: [axis2 ]soap session scope does not work

Hi Deepal, the sessions are working with axis2-1.1.1, i only cannot find how to configure the seesions to expire after some time. I read the Axis2 session management article( http://www.developer.com/java/web/article.php/10935_3620661_2) and it says that they exprire by default within 30 seconds

Re: [axis2 ]soap session scope does not work

Hi Deepal, I have yet another question/issue about the sessions. I am using UsernameToken in a ws security policy handled by rampart. I want to use axis2 sessions so i pass the user/pass only once and then rely on the session to recognize me on a subsequent call.the point is that the rampart

Re: [axis2 ]soap session scope does not work

Nencho If you want to do this, you need to have two different policies. One for the login operation/service, which uses UT, and the other for the rest of the operations, which has encryption (if needed) but no UT. Obviously you need to write your own logic to ensure that you check the session

Re: [axis2 ]soap session scope does not work

Nencho You can specify different policies per operation with Axis2. So you need to identify a specific operation that is the login operation - i.e. the one that users call first (and only first), and statically specify a different policy for this one. I'm not suggesting changing the policy at

Re: [axis2 ]soap session scope does not work

Hi Paul, Thanks for the constructive idea :).anyway,I can't confirm that these services will be invoked only by my client code. Consider some third party client - i cannot force himm to call first the login operation, though it is obvious that the rest of the operations will deny to be

Re: [axis2 ]soap session scope does not work

Hi Paul, Having different policies includes ex-changing them runtime. 1. Is that posible with axis2 without redeploying the service? 2. How this correlates to the session, because i expect different clients to connect to this service and i cannot just change the policiy since one of the will be

Re: [axis2 ]soap session scope does not work

Hi Sanjesh, yes, i have: client.engageModule(new QName(addressing)); in my client - you can take a look at this at Client.java that i attached in my previous post. Thanks, Nencho 2007/4/25, Sanjesh Pathak [EMAIL PROTECTED]: Hi Nencho, Did you engage addressing module on the client

Re: [axis2 ]soap session scope does not work

Hi Anil, Thanks but this is for this but it is about transport session scope and i need soap session scope, where ws addressing come to play and sends an identifier(pretty much like a cookie) that is passed fforth and back. Thanks, Nencho 2007/4/25, Anil Chukkapalli [EMAIL PROTECTED]: You

Re: [axis2 ]soap session scope does not work

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:

Re: [axis2 ]soap session scope does not work

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

Re: [axis2 ]soap session scope does not work

-- *From:* Nencho Lupanov [mailto:[EMAIL PROTECTED] *Sent:* Thursday, April 26, 2007 9:53 AM *To:* axis-user@ws.apache.org *Subject:* Re: [axis2 ]soap session scope does not work Hi Deepal, what about this jira issue: https://issues.apache.org/jira/browse/AXIS2-2561 Does it means that we need

Re: [axis2 ]soap session scope does not work

Nencho Think of this as a cookie. The client has to be enabled to respond with cookies, but that doesn't create the cookie in the first place. To make this work you need to set service scope=soapsession in services.xml Now the server will set the ref params in the reply-to header. If you have

Re: [axis2 ]soap session scope does not work

Hi Paul, I have both scope attribute in services.xml and the setManageSession(true) call in the client, but it still does not work. I attached my service.xml file and my client code. And here is the response that i get frm the server: 3f2 ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope

RE: [axis2 ]soap session scope does not work

Hi Nencho, Did you engage addressing module on the client side? This is required for soap session based communication. Sanjesh _ From: Nencho Lupanov [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 11:14 AM To: [EMAIL PROTECTED]; axis-user@ws.apache.org Subject: [axis2

Re: [axis2 ]soap session scope does not work

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: