Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 5382 invoked from network); 12 Dec 2003 19:28:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Dec 2003 19:28:54 -0000 Received: (qmail 6804 invoked by uid 500); 12 Dec 2003 19:28:34 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 6792 invoked by uid 500); 12 Dec 2003 19:28:34 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Delivered-To: moderator for axis-user@ws.apache.org Received: (qmail 75930 invoked from network); 12 Dec 2003 19:08:53 -0000 Message-ID: <20031212190857.17389.qmail@web80505.mail.yahoo.com> Date: Fri, 12 Dec 2003 11:08:57 -0800 (PST) From: Chetan Lalye Subject: Session Handling and Stateful WS To: axis-user@ws.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-718458883-1071256137=:15495" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --0-718458883-1071256137=:15495 Content-Type: text/plain; charset=us-ascii Hi, I have a couple of questions for the axis gurus.. 1. Session Handling I created a simple stateful webservice by using the SimpleSession Handler and it seemed to work. However I wanted to know how this scales to mutiple users and clients. Are there any limitations ? Are there any other issues that I should be concerned about ? 2. adding SoapHeaders I have written my own handler that adds a Soap Header to Envelope...here's the code snippet. SOAPEnvelope localEnvelope = msg.getSOAPEnvelope(); SOAPHeaderElement header = new SOAPHeaderElement(MYNAMESPACE, MYLOCALART, id); /// id is a Long object containing a long value localEnvelope .addHeader(header); during the execution, there is a exception thrown somewhere in the axis code that "java.lang.Exception: No deserialization context to use in MessageElement.getValueAsType()!" I'm assuming that somewhere its trying to obtain the value of the Header and that must have failed...looks like the header isn't created correctly... Any ideas what could be wrong here ?? thanks Chetan --0-718458883-1071256137=:15495 Content-Type: text/html; charset=us-ascii
Hi,
 
I have a couple of questions for the axis gurus..
 
1. Session Handling
 I created a simple stateful webservice by using the SimpleSession Handler and it seemed to work. However I wanted to know how this scales to mutiple users and clients. Are there any limitations ? Are there any other issues that I should be concerned about ?
 
2. adding SoapHeaders
 
I have written my own handler that adds a Soap Header to Envelope...here's the code
snippet.
 
SOAPEnvelope    localEnvelope = msg.getSOAPEnvelope();
 
SOAPHeaderElement header = new SOAPHeaderElement(MYNAMESPACE,
                        MYLOCALART, id); /// id is a Long object containing a long value
 
localEnvelope .addHeader(header);
 
 
during the execution, there is a exception thrown somewhere in the axis code that
"java.lang.Exception: No deserialization context to use in MessageElement.getValueAsType()!"
 
I'm assuming that somewhere its trying to obtain the value of the Header and that must have failed...looks like the header isn't created correctly... 
 
Any ideas what could be wrong here ??
 
 
 
thanks
Chetan
--0-718458883-1071256137=:15495--