axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chathura Herath <>
Subject [Axis2] Configuration hierarchy no longer extends the WSDLComponents !
Date Sun, 04 Dec 2005 03:32:53 GMT
I was just observing that we no longer extend our Configuration (or
Axis* , AxisOperation, etc) from the relevant WSDL component.
eg AxisOperation (use to) extends WSDLOperation.

I thought that was a nice thing to do because our WOM builder has the
flexibility of building objects out of factory. That is you can ask
the WOM builder to build a AxisOperation object rather than a
WSDLOperation by registering a (AxisDescWSDLComponentFactory). IMO it
is a cleaner way to build the configuration objects rather than
keeping the object inside and delegating ALL the methods which it does
right now.

Is there any good reason why we did this change?


On 12/1/05, Deepal Jayasinghe <> wrote:
> Hi all;
> There was a class called MessageDescription to hold Message level
> information (like WS policy) , but there was no any usage of that class , So
> I removed that class and Added a new class called AxisMessage to do the same
> thing.
> In addition to that removed handler flow data from AxisOperation and moved
> that down to AxisMessage. So now there is a place holder to store WS-policy
> information at the message level as well. In the same time you can add
> message level parameters as well , the way of doing is my adding <message>
> element in <operation> as below;
>    <operation name="echoString">
>         <message label="In">
>             <parameter name="messageIN"
> locked="false">messageIN</parameter>
>         </message>
>     </operation>
> I am sorry for send the mail after I doing this , I really forgot to send
> the mail Im really sorry for that.
> Thanks,
>  Deepal
> ................................................................
> ~Future is Open~

Chathura Herath

View raw message