Return-Path: 
 <axis-user-return-12327-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 5438 invoked by uid 500); 28 Feb 2003 16:40:00 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 5429 invoked from network); 28 Feb 2003 16:40:00 -0000
From: "Hainer Neil" <hainer_neil@bah.com>
To: <axis-user@ws.apache.org>
Subject: RE: Newbie requests help with developing service classes on Axis
Date: Fri, 28 Feb 2003 11:40:10 -0500
Message-ID: <HBEKIJIMMLBOPBEDHIOCIEBHCDAA.hainer_neil@bah.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
In-Reply-To: <B1B1BADE77ACD3119A8800805FC1845B020C93FA@eagle.firepond.com>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Along these lines I have always wondered about the following:

Every example I have seen related to SOAP or Axis either doesn't define a
constructor or defines a constructor that does nothing.  What are the
reasons for this?

What about constructors that require parameters?  I had a discussion with
Rob Englander, author of Java and SOAP, that a class implementing request
level scope requires a no parameter constructor.  This is because of the way
Java implements dynamic loading.  Does this apply to session and application
level scope as well?  I have implemented an init method in my class which is
always called before any other method.  Is there a better approach?

Neil



-----Original Message-----
From: Almeida, Timothy [mailto:timothya@firepond.com]
Sent: Friday, February 28, 2003 11:06 AM
To: 'axis-user@ws.apache.org'
Subject: RE: Newbie requests help with developing service classes on
Axis


There's always the constructor... ;)
I guess the absence of a notion like an init() method is a consequence of
Axis not enforcing implementation of a specific interface [by your service
handler] -- which is nice.
Can you think of a reason why the constructor would not work for you as a
place to do initialization?


-----Original Message-----
From: Milind Gadre [mailto:milind@ecplatforms.com]
Sent: Friday, February 28, 2003 9:59 AM
To: axis-user@ws.apache.org
Subject: Newbie requests help with developing service classes on Axis



Hi,

I am new to Axis and wanted to better understand the protocol for
initializing the object that actually services the SOAP request?
Example, in my deploy.wsdd file I have

  <service name="MyMsgService" style="message">
    <parameter name="className" value="MyMsgServiceClass" />
    <parameter name="allowedMethods" value="processRequest" />
  </service>

Just like with a Servlet, I would like to have some initialization
control over an instance of MyMsgServiceClass. According to the
samples.message.TestMsg class that ships with Axis, there is no
initialization control.

Example: we have the Servlet.init() method that allows the servlet
object to be initialized before any methods are accessed.

Is there a similar protocol for service handlers??

Regards...

Milind Gadre
VP Product Development
ecPlatforms, Inc
901 Mariner's Island Blvd, Suite 565
San Mateo, CA 94404
C: 510.919.0596
E: milind@ecplatforms.com