RE: [aspectwerkz-user] A couple of questions

"AVERY, Neil, FM" <[email protected]> Fri, 14 Oct 2005 16:35:05 +0100
Newsgroups gmane.comp.java.aspectwerkz.user
Message-ID <DDCC15E558B3F142A8F72A157FBB63BE144A6C83@lon0348xns.fm.rbsgrp.net>
Thanks for the reply Alex,

We are using AW2.0

We don't mind trying CVS head but if there is no official release due then
we may be better spending time migrating to AJ5..
is M4 yet feature complete (Im not sure if that's what you mean in ur
reply)?

When is AJ5 final scheduled for release?

-neil.

-----Original Message-----
From: Alexandre Vasseur [mailto:[email protected]] 
Sent: 14 October 2005 16:22
To: [email protected]
Subject: Re: [aspectwerkz-user] A couple of questions


Hi

As you know we merged AspectWerkz technology with AspectJ to produce
"AspectJ 5". This explains the low activity after we shipped the fairly
stable AW 2.0.

AspectJ 5 is in M4 state, and we will do one RC1 more before it gets final,
beeing feature complete with what AspectWerkz syntax brings. I 'll write a
tech. paper to deeply describe the delta / migration path in this timeline
as well.

That said, which version of AW are you using? Is it 2.0 or chs head. CVS
head has changed a lot since 2.0 as I'have been f.e. doing ASM 2.0 upgrade,
backport175 integration, and rearchitected the AspectOf and MixinOf backend
- which indeed as been a weakness so far. As I did not had time (working on
AspectJ 5 integration) and as noone really asked for I never shipped an
official AW 2.1.

I can certainly spend time in a fix for you but :
- what are the chance for you to migrate to AJ 5 final ?
- can you provide me a test case that spot a problem for AW 2.0 (assuming
you are using it)
- can you try with AW-latest by building cvs head ? If the bug is not there
anymore, are you comfortable with using that version?
- can you find a workaround instead?

As you understand, unless there is a high demand for a AW 2.1 I will
certainly encourage everyone to migrate to AspectJ 5 - especially when it
will be final. Alex



On 10/14/05, AVERY, Neil, FM <[email protected]> wrote:
>
> Hi All,
>
> When is the next release of Aspectwerkz?
> Is Aspectwerkz still being actively developed as nothing has happened 
> for the last couple of months.
>
> Ive also found two problems when using aspectwerkz:
> 1. Using Aspects.aspectOf(MyAspect.class, targetInstance) will always 
> return a MyAspect.class instance when one is not bound to 
> targetInstance.
>
> 2. When using java 5 annotations and trying to bind multiple aspects 
> to the same key, only one is ever actually bound (perInstance). This 
> is confirmed when you browse the object instance and can view the 
> instanceAspects hashmap. If you remove the aspect definition which 
> does get bound, then the one which seems to have been hidden will 
> successfully bind.
>
> an example configuration follows:
> <aspect class="org.stuff.RemoteMarshaller" 
> deployment-model="perInstance"
container="org.neo.swarm.aop.AWerkzAOPFactory">
>     <pointcut name="poitcutA">execution(* *..*(..)) AND 
> within(@org.neo.swarm.SomeAnnotation *)</pointcut>
>     <advice name="remote" type="around" bind-to="pointcutA" /> 
> </aspect> <aspect class="org.stuff.ClusteredHandler" 
> deployment-model="perInstance" 
> container="org.neo.swarm.aop.AWerkzAOPFactory">
>     <pointcut name="pointcutB">execution(* *..*(..)) AND 
> within(@org.neo.swarm.SomeAnnotation *)</pointcut>
>     <advice name="remote" type="around" bind-to="pointcutB" /> 
> </aspect>
>
> Any help gratefully appreciated,
> Regards Neil.
>
>
>
> **********************************************************************
> *************
>  The Royal Bank of Scotland plc. Registered in Scotland No 90312.
Registered
> Office: 36 St Andrew Square, Edinburgh EH2 2YB.
>  Authorised and regulated by the Financial Services Authority
>
>  This e-mail message is confidential and for use by the  addressee 
> only. If the message is received by anyone other  than the addressee, 
> please return the message to the sender  by replying to it and then 
> delete the message from your  computer. Internet e-mails are not 
> necessarily secure. The  Royal Bank of Scotland plc does not accept 
> responsibility for  changes made to this message after it was sent.
>
>  Whilst all reasonable care has been taken to avoid the  transmission 
> of viruses, it is the responsibility of the recipient to  ensure that 
> the onward transmission, opening or use of this  message and any 
> attachments will not adversely affect its  systems or data. No 
> responsibility is accepted by The Royal  Bank of Scotland plc in this 
> regard and the recipient should carry  out such virus and other checks 
> as it considers appropriate.  Visit our websites at:
>  http://www.rbs.co.uk/CBFM
>  http://www.rbsmarkets.com
>
****************************************************************************
****
>


***********************************************************************************
The Royal Bank of Scotland plc. Registered in Scotland No 90312.       Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.                                      
Authorised and regulated by the Financial Services Authority     
 
This e-mail message is confidential and for use by the                      
addressee only. If the message is received by anyone other             
than the addressee, please return the message to the sender          
by replying to it and then delete the message from your                    
computer. Internet e-mails are not necessarily secure. The               
Royal Bank of Scotland plc does not accept responsibility for          
changes made to this message after it was sent.                              
                                                                                                        
Whilst all reasonable care has been taken to avoid the                   
transmission of viruses, it is the responsibility of the recipient to        
ensure that the onward transmission, opening or use of this             
message and any attachments will not adversely affect its               
systems or data.  No responsibility is accepted by The Royal           
Bank of Scotland plc in this regard and the recipient should carry   
out such virus and other checks as it considers appropriate.           
                                                                                                               Visit our websites at:                                                                          
http://www.rbs.co.uk/CBFM                                                        
http://www.rbsmarkets.com                                                         
                                                                                                       ********************************************************************************