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 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 2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>: > Nencho > > With any third-party users of your service, you do need to give them > some additional documentation! The WSDL and Policy are a good starting > point, but the developer still needs to understand the business > processes behind the services. > > However, you are right that secureconversation will also give you the > pattern you want, where the initial login is used to create a token, > which is then passed with every request. > > Paul > > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > > 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 executed first. > > > > Maybe i am stick with the Ws Secure conv implemented in rampart, does > > someone has tested it with username token sent only the first time? > > > > > > thanks, > > Nencho > > > > > > 2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>: > > > 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 runtime. That won't work - > > > certainly not at the server side. > > > > > > Paul > > > > > > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > > > > 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 at > > the > > > > login state and another will > > > > be already loged in. > > > > 3. does WS secure conversation way overcome those problems? > > > > > > > > thanks, > > > > Nencho > > > > > > > > > > > > 2007/4/27, Paul Fremantle < [EMAIL PROTECTED]>: > > > > > 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 is available for those other operations. > > > > > > > > > > Paul > > > > > > > > > > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > > > > > > 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 > > > > > > policy > > > > > > is alredy there and will expect a username token in every request. > > > > > > Is there any way to overcome this? > > > > > > > > > > > > thanks, > > > > > > Nencho > > > > > > > > > > > > > > > > > > 2007/4/26, Deepal Jayasinghe < [EMAIL PROTECTED]>: > > > > > > > Hi Nencho, > > > > > > > Yes we found that issue and we have fixed that in the 1.2 branch > > and > > > > the > > > > > > > fixes will be available in 1.2 release. > > > > > > > > > > > > > > Thanks > > > > > > > Deepal > > > > > > > > > > > > > > > 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
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
2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
Nencho
With any third-party users of your service, you do need to give them
some additional documentation! The WSDL and Policy are a good starting
point, but the developer still needs to understand the business
processes behind the services.
However, you are right that secureconversation will also give you the
pattern you want, where the initial login is used to create a token,
which is then passed with every request.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> 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 executed first.
>
> Maybe i am stick with the Ws Secure conv implemented in rampart, does
> someone has tested it with username token sent only the first time?
>
>
> thanks,
> Nencho
>
>
> 2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
> > 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 runtime. That won't work -
> > certainly not at the server side.
> >
> > Paul
> >
> > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > > 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 at
> the
> > > login state and another will
> > > be already loged in.
> > > 3. does WS secure conversation way overcome those problems?
> > >
> > > thanks,
> > > Nencho
> > >
> > >
> > > 2007/4/27, Paul Fremantle < [EMAIL PROTECTED]>:
> > > > 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 is available for those other operations.
> > > >
> > > > Paul
> > > >
> > > > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > > > > 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
> > > > > policy
> > > > > is alredy there and will expect a username token in every
request.
> > > > > Is there any way to overcome this?
> > > > >
> > > > > thanks,
> > > > > Nencho
> > > > >
> > > > >
> > > > > 2007/4/26, Deepal Jayasinghe < [EMAIL PROTECTED]>:
> > > > > > Hi Nencho,
> > > > > > Yes we found that issue and we have fixed that in the 1.2branch
> and
> > > the
> > > > > > fixes will be available in 1.2 release.
> > > > > >
> > > > > > Thanks
> > > > > > Deepal
> > > > > >
> > > > > > > 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 ,
Re: [axis2 ]soap session scope does not work
Nencho
With any third-party users of your service, you do need to give them
some additional documentation! The WSDL and Policy are a good starting
point, but the developer still needs to understand the business
processes behind the services.
However, you are right that secureconversation will also give you the
pattern you want, where the initial login is used to create a token,
which is then passed with every request.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
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 executed first.
Maybe i am stick with the Ws Secure conv implemented in rampart, does
someone has tested it with username token sent only the first time?
thanks,
Nencho
2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
> 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 runtime. That won't work -
> certainly not at the server side.
>
> Paul
>
> On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > 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 at
the
> > login state and another will
> > be already loged in.
> > 3. does WS secure conversation way overcome those problems?
> >
> > thanks,
> > Nencho
> >
> >
> > 2007/4/27, Paul Fremantle < [EMAIL PROTECTED]>:
> > > 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 is available for those other operations.
> > >
> > > Paul
> > >
> > > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > > > 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
> > > > policy
> > > > is alredy there and will expect a username token in every request.
> > > > Is there any way to overcome this?
> > > >
> > > > thanks,
> > > > Nencho
> > > >
> > > >
> > > > 2007/4/26, Deepal Jayasinghe < [EMAIL PROTECTED]>:
> > > > > Hi Nencho,
> > > > > Yes we found that issue and we have fixed that in the 1.2 branch
and
> > the
> > > > > fixes will be available in 1.2 release.
> > > > >
> > > > > Thanks
> > > > > Deepal
> > > > >
> > > > > > 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
>
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 at the
login state and another will
be already loged in.
3. does WS secure conversation way overcome those problems?
thanks,
Nencho
2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
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 is available for those other operations.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> 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
> policy
> is alredy there and will expect a username token in every request.
> Is there any way to overcome this?
>
> thanks,
> Nencho
>
>
> 2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
> > Hi Nencho,
> > Yes we found that issue and we have fixed that in the 1.2 branch and
the
> > fixes will be available in 1.2 release.
> >
> > Thanks
> > Deepal
> >
> > > 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
> > > >
> > > > 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]
> > >
> > >
> > >
> >
> >
> >
> >
> -
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 executed first.
Maybe i am stick with the Ws Secure conv implemented in rampart, does
someone has tested it with username token sent only the first time?
thanks,
Nencho
2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
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 runtime. That won't work -
certainly not at the server side.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> 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 at
the
> login state and another will
> be already loged in.
> 3. does WS secure conversation way overcome those problems?
>
> thanks,
> Nencho
>
>
> 2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
> > 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 is available for those other operations.
> >
> > Paul
> >
> > On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > > 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
> > > policy
> > > is alredy there and will expect a username token in every request.
> > > Is there any way to overcome this?
> > >
> > > thanks,
> > > Nencho
> > >
> > >
> > > 2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
> > > > Hi Nencho,
> > > > Yes we found that issue and we have fixed that in the 1.2 branch
and
> the
> > > > fixes will be available in 1.2 release.
> > > >
> > > > Thanks
> > > > Deepal
> > > >
> > > > > 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
> > > > > >
> > > > > > 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
> > >
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 runtime. That won't work -
certainly not at the server side.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
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 at the
login state and another will
be already loged in.
3. does WS secure conversation way overcome those problems?
thanks,
Nencho
2007/4/27, Paul Fremantle <[EMAIL PROTECTED]>:
> 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 is available for those other operations.
>
> Paul
>
> On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> > 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
> > policy
> > is alredy there and will expect a username token in every request.
> > Is there any way to overcome this?
> >
> > thanks,
> > Nencho
> >
> >
> > 2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
> > > Hi Nencho,
> > > Yes we found that issue and we have fixed that in the 1.2 branch and
the
> > > fixes will be available in 1.2 release.
> > >
> > > Thanks
> > > Deepal
> > >
> > > > 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
> > > > >
> > > > > 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]
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
-
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
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 is available for those other operations.
Paul
On 4/27/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
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
policy
is alredy there and will expect a username token in every request.
Is there any way to overcome this?
thanks,
Nencho
2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
> Hi Nencho,
> Yes we found that issue and we have fixed that in the 1.2 branch and the
> fixes will be available in 1.2 release.
>
> Thanks
> Deepal
>
> > 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
> > >
> > > 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]
> >
> >
> >
>
>
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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
policy
is alredy there and will expect a username token in every request.
Is there any way to overcome this?
thanks,
Nencho
2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
Hi Nencho,
Yes we found that issue and we have fixed that in the 1.2 branch and the
fixes will be available in 1.2 release.
Thanks
Deepal
> 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
> >
> > 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]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 but how do i configure that?
Is that the
30
parameter in axis2.xml?
furthuremore, i made some test with 15 executions with a pause of 4 seconds
and the session doesn't expire.That's 60 seconds.
Thanks,
Nencho
2007/4/26, Deepal Jayasinghe <[EMAIL PROTECTED]>:
Hi Nencho,
Yes we found that issue and we have fixed that in the 1.2 branch and the
fixes will be available in 1.2 release.
Thanks
Deepal
> 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
> >
> > 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]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2 ]soap session scope does not work
Hi Nencho,
Yes we found that issue and we have fixed that in the 1.2 branch and the
fixes will be available in 1.2 release.
Thanks
Deepal
> 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
> >
> > 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]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2 ]soap session scope does not work
Hi Sanjesh, I tried with axis1.1.1 and it works. It fails with axis 1.2. thaks, Nencho 2007/4/26, Sanjesh Pathak <[EMAIL PROTECTED]>: Hi Nencho, I am using Axis2 version 1.1.1 and it is working fine in my local environment here for session scope. What version of Axis2 are you using? I am hosting a sample service that uses session scope accessible at this URL: http://82.165.253.192:8081/axis2/services/SessionService This service takes an OMElement as the parameter and echoes it back. Can you test your client against this service? Sanjesh -- *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 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 > > 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]
RE: [axis2 ]soap session scope does not work
Hi Nencho, I am using Axis2 version 1.1.1 and it is working fine in my local environment here for session scope. What version of Axis2 are you using? I am hosting a sample service that uses session scope accessible at this URL: http://82.165.253.192:8081/axis2/services/SessionService This service takes an OMElement as the parameter and echoes it back. Can you test your client against this service? Sanjesh _ 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 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 > > 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]
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 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 > > 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]
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:
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
>
> 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]
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 can look at the thread "Axis2 Manage Session Cookie Manually" On 4/25/07, Paul Fremantle <[EMAIL PROTECTED] > wrote: > > 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 > > > > in services.xml > > Now the server will set the ref params in the reply-to header. If you > have setManageSession(true) now the client will send them back. > > Paul > > On 4/25/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > > 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 > > > > 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 > > > > > > > -- > Paul Fremantle > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > http://bloglines.com/blog/paulfremantle > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
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 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 ]soap session scope does not work
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
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
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: > 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 > > 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]
Re: [axis2 ]soap session scope does not work
You can look at the thread "Axis2 Manage Session Cookie Manually" On 4/25/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: 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 in services.xml Now the server will set the ref params in the reply-to header. If you have setManageSession(true) now the client will send them back. Paul On 4/25/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > 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 > > 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 > > -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 ]soap session scope does not work 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 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
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
http://www.w3.org/2005/08/addressing"; xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/";>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
" soapenv:mustUnderstand="1">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
" wsu:Id="Timestamp-23612966">2007-04-25T14:52:11.265Z2007-04-25T14:57:11.265Zurn:echo<
wsa:RelatesTo>urn:uuid:D6F41230DE1EAB89901177512730877http://sample01.policy.samples.rampart.apache.org";><
soapenv:Body>http://sample/xsd";>Hello
World
0
Thanks,
Nencho
2007/4/25, Paul Fremantle <[EMAIL PROTECTED]>:
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
in services.xml
Now the server will set the ref params in the reply-to header. If you
have setManageSession(true) now the client will send them back.
Paul
On 4/25/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> 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
>
> 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
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.rampart.samples.policy.sample01.SimpleService
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"; />
http://ws.apache.org/rampart/policy";>
org.apache.rampart.samples.policy.sample01.PWCBHandler
/*
* Copyright 2004,2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.rampart.samples.policy.sample01;
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
import org.apache.neethi.Policy;
import org.apache.neethi.PolicyEngine;
import org.apache.rampart.RampartMessageData;
import javax.xml.namespace.QName;
public class Client {
public static void main(String[] args) throws Exception {
if(args.length != 3) {
System.out.println("Usage: $java Client endpoint_address
client_repo_path policy_xml_path");
}
ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(args[1],
null);
ServiceClient client = new ServiceClient(ctx, null);
Options options = new Options();
options.setAction("urn:echo");
options.setTo(new EndpointReference(args[0]));
options.setManageSession(true);
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
loadPolicy(args[2]));
client.setOptions(options);
client.engageModule(new QName("addressing"));
client.e
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 in services.xml Now the server will set the ref params in the reply-to header. If you have setManageSession(true) now the client will send them back. Paul On 4/25/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: 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 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 -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
