Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <048e01c4d91e$7dc36460$0965a8c0@deepal>
From: "Deepal Jayasinghe" <deepal@opensource.lk>
To: <axis-dev@ws.apache.org>
References: <f8de7ee0412020417295022f0@mail.gmail.com>
 <036b01c4d8f3$6e525ac0$0965a8c0@deepal>
 <f8de7ee041202214843596b71@mail.gmail.com>
Subject: Re: [Axis2][Engine]Step by Step;Engine,
 Engine registry deployment and the Phase Resolver
Date: Fri, 3 Dec 2004 15:57:22 +0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


hi srinath;

1) Keeping the state at the deployment is *BAD* as then the resolver
bind with deployment. And Axis assues all deployment done via one
deployment module.

<<
can axis do deployment via do deployment modules ?

>>

2) keeping a states will create a parellel object Hirachy deployed service

<<
  It is no need to keep them in the deployment module , what it dose is
using the available date
  resolve the phase and give an executable service object to engine registry
, after that it dose not
 keep any state or what ever , only thing it keep in the memory is service
name.
>>


3) We know that the Handlers for the execution Chain comes in at
different time. (e.g. Module comes in at deployment time .. Service
might come at any time) how can we order the handlers if
EngineRegistry forgets handler rules.  So we need to remember the rules
in soe form at registry!

<<
The all the handlers belong to a service described in the service.xml , and
if it want to have modules
then it includes reference to modules , then at the deployment time loaded
the module from EngineRegistry if it has deployed otherwise will throw an
exception. So execution chain will come only at the deployment time.
since we do not provide hot deployment or hot undeployment for modules , I
don't think execution
chain will be change at run time.
so there is no need of keeping phase rule date inside the Engine Registry.

>>

4) It is OK that the resolving done at the *deployment time* my point is
resolver *MUST NOT* use the private states stored inside the
Deployment which bind the resolver to deployment.
resolving can be done by engine(resolve at the first time ..and store)
or deployment.

e.g. What happen if somebody come via JMX and trun on/off handler,
module, service ...

<<
I don't think that even if we keep the Phase resolving with engine registry
we can handle that,
say there are two or three services that has reference to the handler you
are going to turn off, how
can we handle that if we keep PR (phase resolve) inside or with engine
registry ?

its a good use case but the understanding I have is not enough to answer
that

>>

Deepal


----- Original Message ----- 
From: "Srinath Perera" <hemapani@gmail.com>
To: <axis-dev@ws.apache.org>
Sent: Friday, December 03, 2004 11:48 AM
Subject: Re: [Axis2][Engine]Step by Step;Engine, Engine registry deployment
and the Phase Resolver


> > > 1) Engine work with the Deployment just like it happens in Axis 1.1.
> > > Engine knows nothing about the deployment and what it need a
> > > EngineRegistry. The all the deployment do is to generate a Engine
> > > Registry and keep it up to date via hot deployment.
> > >
> > > 2) Phase resolver MUST work on the engine registry and deployment
> > > should not keep private states regarding the deployment apart from the
> > > Engine Registry.
> >
> > <Deepal>
> > In this case I have no idea how we are going to resolve phases. in order
to
> > resolve phase rules that we
> >
> >  should have mechanism of storing phase rules if we try to do it inside
> > engine registry.
> >
> > If we do it at the deployment time by the Deployment module then that
has
> > all the
> >
> > data to resolve the phases, since the required information with the
> > service.xml.
> >
> > And my idea is engineregistry dose not want to know about the phase
rules,
> > it should only know about phases.
> 1) Keeping the state at the deployment is *BAD* as then the resolver
> bind with deployment. And Axis assues all deployment done via one
> deployment module.
> 2) keeping a states will create a parellel object Hirachy deployed service
> 3) We know that the Handlers for the execution Chain comes in at
> differant time. (e.g. Module comes in at deployment time .. Service
> might come at any time) how can we order the handlers if
> EngineRegistry forgets handler rules.  So we need to remeber the rules
> in soe form at registry!
>
>
> > What is the problem of resolving phases rule by the Deployment module at
the
> > deployment time ?  bocz I can't clearly understand why it should be done
by >EngineRegistry.
> It is OK that the resolving done at the *deployment time* my point is
> resolver *MUST NOT* use the private states stored inside the
> Deployment which bind the resolver to deployment.
> resolving can be done by engine(resolve at the first time ..and store)
> or deployment.
> e.g. What happen if somebody come via JMX and trun on/off handler,
> module, service ...
> Cheers
> Srinath
>