Re: Several HTTP session acessing Web Services

[Yashvant chauhan]

use single weservice client and then use this client in javascript and java
too.




On Sun, Jan 3, 2010 at 8:01 AM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:

>
>
>  On Sun, Jan 3, 2010 at 1:52 AM, Bruno Simioni wrote:
>
>> Please, could you give me an example, to solve this problem using
>> WS-Addressing ?
>>
>> My problem is about acess the same service using different clients. One
>> client consumes the service using Javascritp, and the another one, the Java
>> Service Client.
>>
>> Although the Javascript client gets the related message Id, how can I use
>> this on Java Clent?
>>
>
> so your problem is to share a one session among different clients?
>
> I think there is no standard way to do this. even with the http sessions
> you need to copy
> the cookie which contains the JSESSION to other requests.
>
> thanks,
> Amila.
>
>>
>> Regards,
>>
>> Bruno.
>>
>> On Sat, Jan 2, 2010 at 9:53 AM, Yashvant chauhan wrote:
>>
>>> Use WS-Addressing for stateful web service..
>>>
>>>
>>>
>>> On Sat, Jan 2, 2010 at 3:46 PM, Bruno Simioni wrote:
>>>
 Amila, thats about JAX-WS services.

 Here's the situation:

 First Access
 --- HTTP Session 1---
 Client1 (JavaScript) -> Axis2 -> JAX-WS Service1
 --- HTTP Session 1---

 Second Access
 --- HTTP Session 1---
 --- HTTP Session 2---
 Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2
 --- HTTP Session 2---
 --- HTTP Session 1---

 On First Acess, there is one HTTP Session created by my web container
 (Tomcat), and it is used for authentication purposes (application logic).

 On Second Acess, because of WSA, there is two HTTP Sessions!

 How to solve this?

 Bruno.




 n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi <
 amilasuriarach...@gmail.com> wrote:

> in which scope you have deploy your service?
>
> please have a look at here[1].
>
> thanks,
> Amila.
>
> [1] http://wso2.org/library/articles/stateful-web-services-axis2
>
>
> On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni 
> wrote:
>
>> Needing some help with HTTP sessions.
>>
>> When sending a SOAP simple message to Axis2, it create a single HTTP
>> session to handle the client message, and to handle the client HTTP POST
>> request.
>>
>> When sending a WSA SOAP message (by Axis2 Java Client), it creates
>> another http session to handle the WSA soap header, and then process the
>> message. The first one HTTP session persist, but inside any module or
>> webservice, I have only acess to the second one. That´s a problem to me,
>> since I need the first one session, for authorization purposes 
>> (application
>> logic)
>>
>> How to remove this second http session? I need only ONE http session,
>> for all SOAP messages that I send.
>>
>> ps. Client setManageSession(true) does not solve the problem.
>>
>> Regards,
>>
>> Bruno.
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>


>>>
>>>
>>> --
>>> 
>>> Yashvant Singh Chauhan
>>> Mobile- 09845277271
>>> Bangalore
>>>
>>> *
>>>
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 

Yashvant Singh Chauhan
Mobile- 09845277271
Bangalore

*

Re: Several HTTP session acessing Web Services

[Amila Suriarachchi]

On Sun, Jan 3, 2010 at 1:52 AM, Bruno Simioni wrote:

> Please, could you give me an example, to solve this problem using
> WS-Addressing ?
>
> My problem is about acess the same service using different clients. One
> client consumes the service using Javascritp, and the another one, the Java
> Service Client.
>
> Although the Javascript client gets the related message Id, how can I use
> this on Java Clent?
>

so your problem is to share a one session among different clients?

I think there is no standard way to do this. even with the http sessions you
need to copy
the cookie which contains the JSESSION to other requests.

thanks,
Amila.

>
> Regards,
>
> Bruno.
>
> On Sat, Jan 2, 2010 at 9:53 AM, Yashvant chauhan wrote:
>
>> Use WS-Addressing for stateful web service..
>>
>>
>>
>> On Sat, Jan 2, 2010 at 3:46 PM, Bruno Simioni wrote:
>>
>>> Amila, thats about JAX-WS services.
>>>
>>> Here's the situation:
>>>
>>> First Access
>>> --- HTTP Session 1---
>>> Client1 (JavaScript) -> Axis2 -> JAX-WS Service1
>>> --- HTTP Session 1---
>>>
>>> Second Access
>>> --- HTTP Session 1---
>>> --- HTTP Session 2---
>>> Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2
>>> --- HTTP Session 2---
>>> --- HTTP Session 1---
>>>
>>> On First Acess, there is one HTTP Session created by my web container
>>> (Tomcat), and it is used for authentication purposes (application logic).
>>>
>>> On Second Acess, because of WSA, there is two HTTP Sessions!
>>>
>>> How to solve this?
>>>
>>> Bruno.
>>>
>>>
>>>
>>>
>>> n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi <
>>> amilasuriarach...@gmail.com> wrote:
>>>
 in which scope you have deploy your service?

 please have a look at here[1].

 thanks,
 Amila.

 [1] http://wso2.org/library/articles/stateful-web-services-axis2


 On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni 
 wrote:

> Needing some help with HTTP sessions.
>
> When sending a SOAP simple message to Axis2, it create a single HTTP
> session to handle the client message, and to handle the client HTTP POST
> request.
>
> When sending a WSA SOAP message (by Axis2 Java Client), it creates
> another http session to handle the WSA soap header, and then process the
> message. The first one HTTP session persist, but inside any module or
> webservice, I have only acess to the second one. That´s a problem to me,
> since I need the first one session, for authorization purposes 
> (application
> logic)
>
> How to remove this second http session? I need only ONE http session,
> for all SOAP messages that I send.
>
> ps. Client setManageSession(true) does not solve the problem.
>
> Regards,
>
> Bruno.
>



 --
 Amila Suriarachchi
 WSO2 Inc.
 blog: http://amilachinthaka.blogspot.com/

>>>
>>>
>>
>>
>> --
>> 
>> Yashvant Singh Chauhan
>> Mobile- 09845277271
>> Bangalore
>>
>> *
>>
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Several HTTP session acessing Web Services

[Bruno Simioni]

Please, could you give me an example, to solve this problem using
WS-Addressing ?

My problem is about acess the same service using different clients. One
client consumes the service using Javascritp, and the another one, the Java
Service Client.

Although the Javascript client gets the related message Id, how can I use
this on Java Clent?

Regards,

Bruno.

On Sat, Jan 2, 2010 at 9:53 AM, Yashvant chauhan wrote:

> Use WS-Addressing for stateful web service..
>
>
>
> On Sat, Jan 2, 2010 at 3:46 PM, Bruno Simioni wrote:
>
>> Amila, thats about JAX-WS services.
>>
>> Here's the situation:
>>
>> First Access
>> --- HTTP Session 1---
>> Client1 (JavaScript) -> Axis2 -> JAX-WS Service1
>> --- HTTP Session 1---
>>
>> Second Access
>> --- HTTP Session 1---
>> --- HTTP Session 2---
>> Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2
>> --- HTTP Session 2---
>> --- HTTP Session 1---
>>
>> On First Acess, there is one HTTP Session created by my web container
>> (Tomcat), and it is used for authentication purposes (application logic).
>>
>> On Second Acess, because of WSA, there is two HTTP Sessions!
>>
>> How to solve this?
>>
>> Bruno.
>>
>>
>>
>>
>> n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi <
>> amilasuriarach...@gmail.com> wrote:
>>
>>> in which scope you have deploy your service?
>>>
>>> please have a look at here[1].
>>>
>>> thanks,
>>> Amila.
>>>
>>> [1] http://wso2.org/library/articles/stateful-web-services-axis2
>>>
>>>
>>> On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni wrote:
>>>
 Needing some help with HTTP sessions.

 When sending a SOAP simple message to Axis2, it create a single HTTP
 session to handle the client message, and to handle the client HTTP POST
 request.

 When sending a WSA SOAP message (by Axis2 Java Client), it creates
 another http session to handle the WSA soap header, and then process the
 message. The first one HTTP session persist, but inside any module or
 webservice, I have only acess to the second one. That´s a problem to me,
 since I need the first one session, for authorization purposes (application
 logic)

 How to remove this second http session? I need only ONE http session,
 for all SOAP messages that I send.

 ps. Client setManageSession(true) does not solve the problem.

 Regards,

 Bruno.

>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>
>
> --
> 
> Yashvant Singh Chauhan
> Mobile- 09845277271
> Bangalore
>
> *
>

Re: WS-Eventing

[Yashvant chauhan]

Hi,

I tried Savan eventing Sample there were one PublisherService and two
ListenerService.
Client able to subscribe a Service but not able to get the Notification how
I updates the Client.java to get the generated notification

Regards,
yashvant

On Tue, Dec 29, 2009 at 12:27 AM, Gilbert Pilz wrote:

> Hi Martin,
>
> Sorry, I'm missing a bit of context here. RIA events? WS-Eventing supports
> the "Subscribe" operation. What you are subscribing to is outside the scope
> of WS-Eventing.
>
> - gp
>
> On 12/26/2009 6:55 PM, Martin Gainty wrote:
>
> Good Evening Gilbert
>
> In the other apache projects we've registered listeners to predefined RIA
> events such as ContainerStart,SessionStart,SessionEnd..I would be very
> interested to know if this registration process for known RIA events is
> supported by WS-Eventing or is there some other algorithm implmenented to
> register the events and/or configure a custom dispatcher to dispatch to the
> correct listener
>
> thanks,
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>
> --
> Date: Sat, 26 Dec 2009 16:26:24 -0800
> From: gilbert.p...@oracle.com
> To: axis-user@ws.apache.org
> Subject: Re: WS-Eventing
>
> If you are interested in WS-Eventing, you might want to keep an eye on what
> is going on at the W3C Web Services Resource Access Working Group [1] which
> is working on standardizing (among other things) WS-Eventing.
>
> [1] http://www.w3.org/2002/ws/ra/
>
> Gilbert Pilz | Standards Architect | Middleware Standards | Oracle
> Corporation
>
> On 12/23/2009 12:46 PM, Prabath Siriwardena wrote:
>
> Please have a look at [1].
>
> Thanks & regards.
> -Prabath
>
> [1]: http://blog.facilelogin.com/search/label/Savan
>
> Yashvant chauhan wrote:
>
> How I can develope a WS-Eventing in Axis2
>
>
>
>
>
>
>
> --
> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up
> now. 
>
>


-- 

Yashvant Singh Chauhan
Mobile- 09845277271
Bangalore

*

Re: Several HTTP session acessing Web Services

[Yashvant chauhan]

Use WS-Addressing for stateful web service..



On Sat, Jan 2, 2010 at 3:46 PM, Bruno Simioni wrote:

> Amila, thats about JAX-WS services.
>
> Here's the situation:
>
> First Access
> --- HTTP Session 1---
> Client1 (JavaScript) -> Axis2 -> JAX-WS Service1
> --- HTTP Session 1---
>
> Second Access
> --- HTTP Session 1---
> --- HTTP Session 2---
> Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2
> --- HTTP Session 2---
> --- HTTP Session 1---
>
> On First Acess, there is one HTTP Session created by my web container
> (Tomcat), and it is used for authentication purposes (application logic).
>
> On Second Acess, because of WSA, there is two HTTP Sessions!
>
> How to solve this?
>
> Bruno.
>
>
>
>
> n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi <
> amilasuriarach...@gmail.com> wrote:
>
>> in which scope you have deploy your service?
>>
>> please have a look at here[1].
>>
>> thanks,
>> Amila.
>>
>> [1] http://wso2.org/library/articles/stateful-web-services-axis2
>>
>>
>> On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni wrote:
>>
>>> Needing some help with HTTP sessions.
>>>
>>> When sending a SOAP simple message to Axis2, it create a single HTTP
>>> session to handle the client message, and to handle the client HTTP POST
>>> request.
>>>
>>> When sending a WSA SOAP message (by Axis2 Java Client), it creates
>>> another http session to handle the WSA soap header, and then process the
>>> message. The first one HTTP session persist, but inside any module or
>>> webservice, I have only acess to the second one. That´s a problem to me,
>>> since I need the first one session, for authorization purposes (application
>>> logic)
>>>
>>> How to remove this second http session? I need only ONE http session, for
>>> all SOAP messages that I send.
>>>
>>> ps. Client setManageSession(true) does not solve the problem.
>>>
>>> Regards,
>>>
>>> Bruno.
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>


-- 

Yashvant Singh Chauhan
Mobile- 09845277271
Bangalore

*

Re: Several HTTP session acessing Web Services

[Bruno Simioni]

Amila, thats about JAX-WS services.

Here's the situation:

First Access
--- HTTP Session 1---
Client1 (JavaScript) -> Axis2 -> JAX-WS Service1
--- HTTP Session 1---

Second Access
--- HTTP Session 1---
--- HTTP Session 2---
Client1 (Java, Service Client, WSA) -> Axis2 -> JAX-WS Service2
--- HTTP Session 2---
--- HTTP Session 1---

On First Acess, there is one HTTP Session created by my web container
(Tomcat), and it is used for authentication purposes (application logic).

On Second Acess, because of WSA, there is two HTTP Sessions!

How to solve this?

Bruno.



n Sat, Jan 2, 2010 at 12:10 AM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:

> in which scope you have deploy your service?
>
> please have a look at here[1].
>
> thanks,
> Amila.
>
> [1] http://wso2.org/library/articles/stateful-web-services-axis2
>
>
> On Fri, Jan 1, 2010 at 7:05 PM, Bruno Simioni wrote:
>
>> Needing some help with HTTP sessions.
>>
>> When sending a SOAP simple message to Axis2, it create a single HTTP
>> session to handle the client message, and to handle the client HTTP POST
>> request.
>>
>> When sending a WSA SOAP message (by Axis2 Java Client), it creates another
>> http session to handle the WSA soap header, and then process the message.
>> The first one HTTP session persist, but inside any module or webservice, I
>> have only acess to the second one. That´s a problem to me, since I need the
>> first one session, for authorization purposes (application logic)
>>
>> How to remove this second http session? I need only ONE http session, for
>> all SOAP messages that I send.
>>
>> ps. Client setManageSession(true) does not solve the problem.
>>
>> Regards,
>>
>> Bruno.
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>