"Your ticket is handled at the application level where the ticket is passed to the application (the service class) and then the business logic code checks for the compatibility of the ticket ?"
Yes.. true. I have to implement specific method calls on my web service. The first method called by the client authenticates them.. then I give them back a "ticket" string. Then the client calls a possible 5 other methods which are always receiving the "ticket" string which I sent to the client. I have no control over the client as it was developed by Intuit and I'm just implementing my Web Service to fit their wsdl. "If so you would not be able to use the addressing reference properties to make it work. Addressing reference properties are a means of handling sessions and other stuff without the application being aware!" Unfortunately I guess this seems to be the case. Because of the requirements of the methods that the client is expecting to call, I will have to handle the session maintenance and ticket tracking within the application itself. Attached is the wsdl I have to implement for my Web Service, but here is a basic breakdown of the methods that the client calls, so you can see why I have to handle everything in the app: - public java.lang.String[] authenticate(java.lang.String strUserName, java.lang.String strPassword) - public java.lang.String sendRequestXML(java.lang.String ticket, java.lang.String strHCPResponse, java.lang.String strCompanyFileName, java.lang.String qbXMLCountry, int qbXMLMajorVers, int qbXMLMinorVers) - public int receiveResponseXML(java.lang.String ticket, java.lang.String response, java.lang.String hresult, java.lang.String message) - public java.lang.String connectionError(java.lang.String ticket, java.lang.String hresult, java.lang.String message) - public java.lang.String getLastError(java.lang.String ticket) - public java.lang.String closeConnection(java.lang.String ticket) Brian Russell www.closerware.com -----Original Message----- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 1:55 AM To: [email protected]; [EMAIL PROTECTED] Subject: Re: [Axis2] Maintaining Session Ticket Hi, Lemme get your problem first :) Your ticket is handled at the application level where the ticket is passed to the application (the service class) and then the business logic code checks for the compatibility of the ticket ? If so you would not be able to use the addressing reference properties to make it work. Addressing reference properties are a means of handling sessions and other stuff without the application being aware! Ajith On 6/14/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > 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 > > > > -- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
QBWebConnectorSvc.wsdl
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
