Return-Path: 
 <axis-dev-return-4079-apmail-xml-axis-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org
Received: (qmail 86236 invoked by uid 500); 6 Nov 2001 21:03:07 -0000
Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
list-help: <mailto:axis-dev-help@xml.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@xml.apache.org>
list-post: <mailto:axis-dev@xml.apache.org>
Delivered-To: mailing list axis-dev@xml.apache.org
Received: (qmail 86227 invoked from network); 6 Nov 2001 21:03:07 -0000
Message-ID: <4F47DCFADC8DD5118D2B00508B952D9668089C@salsa.allaire.com>
From: Glen Daniels <gdaniels@macromedia.com>
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
Subject: WSDD - proposed change
Date: Tue, 6 Nov 2001 16:02:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


I'd like to make service deployment easier - WSDD is great (and simple!) in
a number of ways, but the whole service/provider configuration isn't one of
them.  Here's a proposed new scheme:

Instead of <provider> elements which sit inside the service element, we have
a service type attribute which is a QName:

<service name="MyService" type="java:RPC">

Preregistered ones include java:RPC, java:Message, java:EJB, and
axis:Handler.  New ones are pluggable.

Now the issue becomes getting provider-specific options in the right place.
The way the code works right now is that there is a single shared instance
of each type of provider, which pulls options from the Service itself, so I
propose we leave it that way -

<service name="MyService" type="java:RPC">
 <parameter name="className" value="glen.TestService"/>
 <parameter name="methodName" value="*"/>
 <parameter name="otherServiceSpecificOption" value="foo"/>
</service>

What do you think?

--Glen