Re: [aspectwerkz-user] Hot deployment questions

this preparation step made by the deployment scope construct is only
necessary for execution pointcuts, since they are the only ones that
triggers a schema change (since we need to add a method to implement
this construct).

However, this distinction has not been made in the current
implementation (although it would not be hard to do so).

/Jonas

On Apr 10, 2005 11:57 PM, Vincent Massol <[email protected]> wrote:
> Hi Michael,
> 
> I believe the reason it works is simply because the modified classes are not
> yet loaded by the classloader when the aspects are weaved using hot
> deployment. Otherwise, I believe it won't work and a deployment scope would
> be needed.
> 
> In other words, it's only by chance that it works and in general you should
> always use a deployment scope when doing hot deployment.
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: Michael Haupt [mailto:[email protected]]
> > Sent: dimanche 10 avril 2005 18:19
> > To: [email protected]
> > Subject: RE: [aspectwerkz-user] Hot deployment questions
> >
> > Hi Vincent,
> >
> >
> > Vincent Massol said:
> > > Thanks you very much Mihir, that's very helpful. I have found that it
> > > works without any aop.xml and without Deployment Scope.
> >
> >
> > could you please post your source code (or a very small example)? I'm
> > interested in knowing how hot deployment works without aop.xml and
> > deployment scopes.
> >
> > Best,
> >
> >
> > Michael Haupt
> >
> 
> 


-- 
/Jonas