Return-Path: 
 <axis-user-return-40203-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 77942 invoked from network); 19 Jan 2006 08:43:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Jan 2006 08:43:50 -0000
Received: (qmail 49103 invoked by uid 500); 19 Jan 2006 08:43:37 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 48767 invoked by uid 500); 19 Jan 2006 08:43:35 -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@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 48754 invoked by uid 99); 19 Jan 2006 08:43:34 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2006 00:43:34 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_PASS,UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of D.Lopez@uib.es designates
 130.206.33.5 as permitted sender)
Received: from [130.206.33.5] (HELO T1.UIB.ES) (130.206.33.5)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2006 00:43:31 -0800
Received: from CONVERSION-DAEMON.uib.es by uib.es (PMDF V6.2-X27 #31095)
 id <01LXY1A73RLC97OFXG@uib.es> for axis-user@ws.apache.org; Thu,
 19 Jan 2006 09:43:02 +0100
Received: from [172.20.2.77] (uib002077.int.uib.es [172.20.2.77])
 by uib.es (PMDF V6.2-X27 #31095) with ESMTP id <01LXY1A3AA7I8Y9KID@uib.es>
 for
 axis-user@ws.apache.org; Thu, 19 Jan 2006 09:42:56 +0100
Date: Thu, 19 Jan 2006 09:42:52 +0100
From: =?ISO-8859-1?Q?Daniel_L=F3pez?= <D.Lopez@uib.es>
Subject: Re: Web Service requests dispatcher
In-reply-to: <bf414ee60601180624t390b9599kacc70d1766bb2b09@mail.gmail.com>
To: axis-user@ws.apache.org
Reply-to: D.Lopez@uib.es
Message-id: <43CF510C.4090605@uib.es>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 8BIT
X-Accept-Language: es,ca,en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.7.12)
 Gecko/20050915
References: <43CE411E.1040809@uib.es>
 <bf414ee60601180624t390b9599kacc70d1766bb2b09@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Anne,
Thanks for your suggestions, I tried the java:MSG provider and even
though it goes one step further towards what I want to accomplish, I'm
still limited to make it so the name of the operation and method in the
Java class are the same, which I want to avoid if possible. Is there any
way I can change that?

I also had already considered the workaround you suggest with the
submitRequest generic operation, but then I would lose the extra
features that I can get from defining each operation separatedly in the
wsdd, each one with its parameters and types specified etc.

So I would like to be able to do something like...
...
<service name="TestWebService" provider="java:MSG">
   <parameter name="className" value="test.TestWS" />
   <parameter name="scope" value="Application" />
   <parameter name="allowedMethods" value="process" />
   <operation
     name="getInfo"
     qname="ns:getInfo"
     returnQName="return"
     returnType="rtns:normalizedString"
     xmlns:rtns="http://www.w3.org/2001/XMLSchema"
     xmlns:ns="http://soapinterop.org/xsd"
    >
      <parameter name="id" type="tns:string"
                 xmlns:tns="http://www.w3.org/2001/XMLSchema"
      />
   </operation>
   <operation
     name="getMoreInfo"
     qname="ns:getMoreInfo"
     returnQName="return"
     returnType="rtns:normalizedString"
     xmlns:rtns="http://www.w3.org/2001/XMLSchema"
     xmlns:ns="http://soapinterop.org/xsd"
    >
      <parameter name="id" type="tns:string"
                 xmlns:tns="http://www.w3.org/2001/XMLSchema"
      />
      <parameter name="anotherParam" type="tns:string"
                 xmlns:tns="http://www.w3.org/2001/XMLSchema"
      />
   </operation>
   ...
  </service>
...
But have both the operations,"getInfo" and "getMoreInfo" be implemented
in a single Java method like
/**
*
*/
public Element [] dispath(Element [] elems)
{
   // Parse elems and see if the requested operation is getInfo
   // or getMoreInfo...
}

Is this possible at all?
Thanks,
D.


Anne Thomas Manes escribi�:
> You can have complete control over dispatching if you use a message 
> style service with the java:MSG provider. Alternatively, you can define 
> a generic operation (something like "submitRequest") which will always 
> be dispatched to your controller.
> 
> Anne