"Seems your interaction goes beyond a simple IN-OUT MEP. So if you want to maintain this you can either define a custom MEP or use WS-Addressing replyTo mechanism to pass your ticket here and there."
It looks as though I will have to come up with something custom for passing tickets back and forth. This "ticket" is just some made up string that would allow me to track that this is the same communication "session" (along with some other things I can check) so that I can verify that I'm talking to the same client, and where I am in the communication process. As I had mentioned, I had hoped to do this using HttpSession, but I don't think it's possible. I really have no knowledge of SOAP or any of the "guts" of Axis.. so really want to just use it to serve my Web Service while I worry about the business logic of what the service actually is supposed to do. I will have to look at WS-Adressing but as you said, I think my implementation goes beyond just a simple IN-OUT MEP. The client is going to make specific method calls (which contain this ticket string) to my WS which I cannot change, so that's all I have to work with. "Is your client also uses Axis2 as the client. setting options.setManageSession(true), Axis2 client will automatically do it without client being worried about it. But if the clients are using some other clients, then they have to explicitly do this." No. This is Intuit's client program that they developed and I have no control over. "In Axis2 we do not have static methods in MessageContext. If you wanna access message context within your skeleton, read this : http://www.wso2.net/kb/106."; Thanks! This will likely be useful as I learn more of what my capabilities are in Axis2. Brian Russell www.closerware.com -----Original Message----- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:04 AM To: [email protected] Subject: Re: [Axis2] Maintaining Session Ticket Brian Russell wrote: > > > 1. Has anyone worked with maintaining session specifically with > regard to the Quickbooks Web Connector v.1.0.52 and Axis2 v.1.0 on > Tomcat 5 (I'm using v.5.5.15)? > > a. If not, does anyone have any suggestions for implementing this > session maintenance by passing this ticket (which is just a String) back > to the client, who sends it back to the server on subsequent calls until > the final closing call? Before I answer this questions, let explain two concepts. 1. Using WS-Addressing, if some one gets reference parameters within replyTo header, then he needs to send out thr reference parameters back to the place in his response. 2. Depending on the number and direction of messages happening, we define a message exchange pattern (MEP). Seems your interaction goes beyond a simple IN-OUT MEP. So if you want to maintain this you can either define a custom MEP or use WS-Addressing replyTo mechanism to pass your ticket here and there. Is your client also uses Axis2 as the client. setting options.setManageSession(true), Axis2 client will automatically do it without client being worried about it. But if the clients are using some other clients, then they have to explicitly do this. > > 2. I will most likely be needing to access the HttpSession in the > skeleton class for my web service, based on what I've read in the > archives, that would look something like this: > MessageContext messageContext = MessageContext.getCurrentContext(); In Axis2 we do not have static methods in MessageContext. If you wanna access message context within your skeleton, read this : http://www.wso2.net/kb/106. -- Chinthaka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
