axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <g...@thoughtcraft.com>
Subject RE: [Axis2] Deployment
Date Fri, 10 Dec 2004 17:00:43 GMT

Hi all!

I'm still at my meeting in Orlando, so am occasionally connected - wow, lots
of mail in the past couple of days!  Am catching up, but here's my take on
this one.

The <operation> in Axis 1.X has both a required name and optional qname
attribute for a couple of reasons - first, all operations are referred to by
name (String) in the hashtable inside ServiceDesc, and these names
correspond precisely to the Java methods when using back-end classes to
implement your services.  Second, the qname attribute allows the user (or
the WSDL->WSDD generator) to change the default "body qname" for the XML
element which maps to this operation on the wire.  If it isn't there, we
just synthesize the QName by using the service namespace and the operation
name - the standard RPC pattern.

For Axis 2.0, I think we should start out pretty basic, and think about
sticking as closely as possible to the WSDL 2 object model.  So for right
now, since we're not particularly doing anything operation specific, I think
we only need the ability to map a particular message to a particular
AxisOperation object.

In WSDL 2, an operation may be uniquely differentiated by a tuple consisting
of the interface QName and an operation NCName.  Since a WSDL service has a
single "most derived" interface already, I think we should have a syntax
something like this for providing deployment information about our
operations:

<service interface="ns:mostDerived">
 <operation name="op1"/>
 <interface qname="ns:parentInterface">
   <operation name="foo"/>
 </interface>
</service>

The idea is that you can use the shorthand of specifying <operation>
directly inside <service> if you're talking about operations that are
directly in the service's interface.  When you want to include metadata for
operations in ancestor interfaces, you'll need to group them by the
interface QName.

Right now (for M1) the only purpose for this would be to create
AxisOperation components and make them available in the MessageContext as
appropriate.  Soon we'd want to flesh out what can go inside the <operation>
elements (handler references, property settings, etc), and add the ability
to map AxisOperation objects to particular back-end Java methods.

Thoughts?

--Glen

> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk] 
> Sent: Friday, December 10, 2004 5:09 AM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2] Deployment
> 
> Hmmm. IIRC the qname was optional right? Basically the idea 
> was to provide an alternate name for the operation .. if the 
> name in the WSDL wasn't what showed up on the wire for example.
> 
> Glen or Dims will be able to confirm .. let's wait until they 
> wake up and ack.
> 
> BTW, are we going to have any operation specific things in 
> service.xml for M1? I thought the plan was to go simple and 
> just have service-wide deployment info.
> 
> Sanjiva.
> 
> ----- Original Message -----
> From: Deepal Jayasinghe
> To: axis-dev@ws.apache.org
> Sent: Friday, December 10, 2004 2:38 PM
> Subject: Re: [Axis2] Deployment
> 
> 
> hi all;
> 
> I didn't get any reply to this mail , so can I assume that it 
> cant have both
> name and qname attributes ?
> 
> Deepal
> 
> 
> ----- Original Message ----- 
> From: Deepal Jayasinghe
> To: axis-dev@ws.apache.org
> Sent: Friday, December 10, 2004 12:21 PM
> Subject: [Axis2] Deployment
> 
> 
> hi all;
> 
> I am sorry I forget to make subject correctly :( , and it has 
> gone to axis
> dev
> 
> 
> service.xml which is described in wiki page
> (http://wiki.apache.org/ws/FrontPage/Architecture/Deployment )
> it can see a tag like below
> 
> <operation name=".." qname="..." style=".." use="..">
> 
> do we really need both name and qname attributes for operation?
> 
> 
> Deepal
> 
> 
> ==================================================
> Deepal Jayasinghe
> Lanka Software Foundation
> 0714 817 310
> 
> 

Mime
View raw message