Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-dev] Load-Time Weaving and "declare precedence ..."

can you open a bugzilla for that one ? The concrete aspect makes sense indeed.
Alex

On 8/4/05, Matthew Webster <matthew_webster@xxxxxxxxxx> wrote:
> 
> 
> 
> 
> Alex,
> 
> The behaviour when declaring precedence using XML should be the same as
> using an aspect: if there is any conflict you will get an error:
> 
>    conflicting declare precedence orderings for aspects: precedence.B and precedence.A    Test.java   Test AspectJ/src/precedence
> 
> I think the issue of conflict is already well covered. However this raises
> the point that precedence must be declared within the scope of a concrete
> aspect:
> 
> <aspectj>
>       <aspects>
>             <concrete-aspect
>                   name="com.xyz.MyPrecedence"
>                   precedence="*..*Security*, Logging+, *"
>             />
>       </aspects>
> </aspectj>
> 
> which says a concrete aspect must contain either an extends or a precedence
> attribute.
> 
> Matthew Webster
> AOSD Project
> Java Technology Centre, MP146
> IBM Hursley Park, Winchester,  SO21 2JN, England
> Telephone: +44 196 2816139 (external) 246139 (internal)
> Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
> http://w3.hursley.ibm.com/~websterm/
> 
> Alexandre Vasseur <avasseur@xxxxxxxxx>@eclipse.org on 04/08/2005 08:56:09
> 
> Please respond to AspectJ developer discussions <aspectj-dev@xxxxxxxxxxx>
> 
> Sent by:    aspectj-dev-bounces@xxxxxxxxxxx
> 
> 
> To:    AspectJ developer discussions <aspectj-dev@xxxxxxxxxxx>
> cc:
> Subject:    Re: [aspectj-dev] Load-Time Weaving and "declare precedence
>        ..."
> 
> 
> that 's nice
> How would we handle the case where f.e.:
> 
> aspect A {
>   declare precedence A, B
> }
> aspect B { }
> xml precedence="B, A"
> 
> In a XML-driven precedence only model that could not happen, but
> obviously we are not there.
> Also there can be conflict in the XML declared precedence as soon as
> there is 1+ XML file that configures a weaver instance - which we have
> due to classpath searching (META-INF/aop.xml)
> 
> Alex
> 
> 
> On 8/4/05, Matthew Webster <matthew_webster@xxxxxxxxxx> wrote:
> >
> >
> >
> >
> > Alex,
> >
> > Precedence is an ordered list of type patterns with no more than one
> > wildcard
> > (
> http://www.eclipse.org/aspectj/doc/released/progguide/semantics-declare.html#d0e6802
> )
> >  so how about:
> >
> > <aspectj>
> >       <aspects>
> >             <precedence>
> >                   <aspect name="*..*Security*"/>
> >                   <aspect name="Logging+"/>
> >                   <aspect name="*"/>
> >             </precedence>
> >       </aspects>
> > </aspectj>
> >
> > or a shorthand form:
> >
> > <aspectj>
> >       <aspects precedence="*..*Security*, Logging+, *"/>
> > </aspectj>
> >
> > Matthew Webster
> > AOSD Project
> > Java Technology Centre, MP146
> > IBM Hursley Park, Winchester,  SO21 2JN, England
> > Telephone: +44 196 2816139 (external) 246139 (internal)
> > Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
> > http://w3.hursley.ibm.com/~websterm/
> >
> > Alexandre Vasseur <avasseur@xxxxxxxxx>@eclipse.org on 03/08/2005 17:53:36
> >
> > Please respond to AspectJ developer discussions <aspectj-dev@xxxxxxxxxxx>
> >
> > Sent by:    aspectj-dev-bounces@xxxxxxxxxxx
> >
> >
> > To:    AspectJ developer discussions <aspectj-dev@xxxxxxxxxxx>
> > cc:
> > Subject:    Re: [aspectj-dev] Load-Time Weaving and "declare precedence
> >        ..."
> >
> >
> > We provided precedence control thru the XML declaration ordering in
> > AspectWerkz - is that what you are looking for ? Could you perhaps
> > sketch on how the xml snip would look like ?
> > Alex
> >
> > On 8/3/05, Matthew Webster <matthew_webster@xxxxxxxxxx> wrote:
> > >
> > >
> > >
> > >
> > > The current AspectJ 5 specification allows simple concrete aspects to
> be
> > > defined in aop.xml. They may extend an abstract aspect and define a
> > single
> > > "scoping" pointcut. I think it would be very useful to be able to
> declare
> > > aspect precedence in a similar way allowing aspects to be deployed
> > without
> > > any specific precedence leaving any decision to a systems
> administrator.
> > >
> > > Matthew Webster
> > > AOSD Project
> > > Java Technology Centre, MP146
> > > IBM Hursley Park, Winchester,  SO21 2JN, England
> > > Telephone: +44 196 2816139 (external) 246139 (internal)
> > > Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
> > > http://w3.hursley.ibm.com/~websterm/
> > >
> > > _______________________________________________
> > > aspectj-dev mailing list
> > > aspectj-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> > >
> > _______________________________________________
> > aspectj-dev mailing list
> > aspectj-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> >
> >
> > _______________________________________________
> > aspectj-dev mailing list
> > aspectj-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> >
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
> 
> 
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>


Back to the top