Perfect :)
This gives the necessary flexibilty for the module to act properly when engaged.
+1 from meOn 1/10/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1 from me.-- Ajith Ranabahu
> >
> > ~Future is Open~
> >
> > ----- Original Message -----
> > From: "Sanka Samaranayake" <[EMAIL PROTECTED]>
> > To:
> > Sent: Monday, January 09, 2006 1:07 PM
> > Subj
xisDescription) in module
interface.
Thanks,
Sanka
>
> Thanks,
> Deepal
>
> ~Future is Open~
>
> - Original Message -
> From: "Sanka Samaranayake" <[EMAIL PROTECTED]>
> To:
> Sent:
.
Thanks,
Deepal
~Future is Open~
- Original Message -
From: "Sanka Samaranayake" <[EMAIL PROTECTED]>
To:
Sent: Monday, January 09, 2006 1:07 PM
Subject: Re: [Axis2] Inform module when they enagage to system
On Mon, 2006-01-09 at 13:07 +0600, Sanka Samaranayake wrote:
> 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
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 functionalitie
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
cha
