Re: [Axis2] Inform module when they enagage to system

[Deepal Jayasinghe]

Hi Sanka ;

I am not telling to add three init methods , what I want is to modify the 
init method in the useful way , giving AxisConfiguration is not enough for 
module , they might need to add some data to context at the init time there 
for rather than giving AxisConfiguration we need to pass 
ConfigurationConetxt and ModuleDecription corresponding to that module.

I also like to have one engage() method in Module interface rather than 
overloading methods , in that case we need to have a parent for each Axis* 
(AxisService , AxisOperation etc) , well that also not a bad idea to do.

Thanks,
Deepal
................................................................
~Future is Open~

----- Original Message ----- 
From: "Sanka Samaranayake" <[EMAIL PROTECTED]>
To: <axis-dev@ws.apache.org>
Sent: Monday, January 09, 2006 1:07 PM
Subject: Re: [Axis2] Inform module when they enagage to system


Hi guys,

+1 for notifying a module when it is engaged. It allows the module to
put its configuration information in terms of policies in the
description classes (AxisServce .. etc) in the correct hierarchy.  It
also allow the module to prevent a service being depolyed if it
requires functionalities which the module is incapable of providing.

One more suggestion .. Rather than adding three init(..) methods with
different signatures can't we add a single init(..) method which takes
a single type which should be the base class of AxisService,
AxisOperation .. etc. I suggest we do bit of refactoring and extract
this base class where we can put all the common logic like adding
policies ..etc.

Best,
Sanka

On 1/9/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

Hi all;

when we engage a module to somewhere in the system (to system , to a 
service
, to an operation) we are not going to inform module about that , but I
think we need to allow module to add its policy , parameters and so on 
into
corresponding descriptions. To support that I need to change Module
interface. And I think we need to add following two methods into it and 
need
to change its init method to take configurationconetext and
ModuleDescription as arguments.

Interface Module {

void init(ConfigurationConetext configContext , ModuleDescriptoion
moduledesc) throws AxisFault ;

void engage(AxisService service)  throws AxisFault ;


void engage(AxisOperation operation)  throws AxisFault ;

}





Thanks,
 Deepal
................................................................
~Future is Open~