Re: [aspectwerkz-user] [poll] what are you (still) using AspectWerkz for

We are still using AspectWerkz 2 for compile 
time/offline declarative transaction demarcation using Java 5 annotations.

I actually started looking at AspectJ 1.5 just 
the other day. Although I looked rather briefly, 
I was surprised to see that much of the 
documentation seemed to assume previous knowledge 
of the old AspectJ syntax. It also took me a 
while to figure out that XML definitions only 
work for load-time weaving. The latter makes me a 
bit worried. I have put some effort into 
minimizing round-trip time 
(code-compile-runt-test) in our dev environment. 
For this reason I created a plugin for IntelliJ 
(<http://intellij.expertsystems.se/>http://intellij.expertsystems.se/) 
that would do offline weaving of recompiled 
files. If we change 1 file, 1 file will be compiled and 1 file will be weaved.
With AspectJ, it seems from the documentation I 
have to point out the directory containing the 
(compiled) aspect. That means AspectJ would need 
to process our 1800+ classes to find our 1 aspect 
and then weave the (possibly single) changed 
class(es). I'm worried about the effect on 
performance. (Although I could have a plugin 
require an XML definition file, I would prefer to 
keep it non-intrusive and zero configuration if possible).
Please note, however, that I have not actually tried AspectJ yet.

Documentation particularly aimed at AW users could be helpful.
Personally I could also see benefits (performance 
and easier migration) of AspectJ supporting XML 
definitions for offline weaving.

Another tip would be to update the AspectWerkz 
website to recommend AspectJ for new projects.


At 2006-09-28 21:53, Alexandre Vasseur wrote:
>Hi all
>
>I am glad to see that some of you are using 
>AspectWerkz and some of its advanced features - 
>as far as I can assume from the latest posts on 
>this list. This always amazes me that 
>AspectWerkz reaches its 3rd years - a bit more if we include alpha work.
>I would like to start a poll to better 
>understand who is "still" using AspectWerkz and 
>for who ensuring correct and fast answers thru this list is critical.
>
>As you may know more than a year ago we started 
>a merge with AspectJ 
>(<http://aspectj.org>http://aspectj.org) that 
>Jonas and myself conducted successfully bringing 
>most of the AspectWerkz features to AspectJ. 
>What might be not in AspectJ is primarily hot 
>deployment of aspects though the AspectJ if 
>pointcut (also available with the XML or 
>annotation based syntax) addresses this use case.
>All others features including plain Java AOP 
>with no new keywords and a huge range of others 
>features (including Eclipse integration) is 
>right there in AspectJ - which further benefits 
>from a nice integration with the Spring framework.
>
>As working upfront on two projects (and a bunch 
>of others activities) is fairly time consuming 
>for Jonas and myself I can only put shame on 
>both of us for the slow support answers you get from this list.
>I thus would like to know (reply privately if 
>you prefer, to me and cc jboner at <http://codehaus.org>codehaus.org)
>- if you feel stuck or annoyed by the slow support you get from this list
>- if you still have AW running in your system
>- if you plan to migrate to AspectJ
>- whatever you'd expect from us the core guys 
>(we never wrote a AspectWerkz to AspectJ migration guide f.e.)
>- if you'd like some help 
>(architecture/coding/validation) to migrate your system
>
>Thanks
>Alex


----------

Email: 
<mailto:[email protected]>[email protected] 
• Web: <http://www.expertsystems.se/>www.expertsystems.se
Mobile: +46-(0)735-16 34 13 • Skype: <callto://mattiasj78>mattiasj78
Address: Göteborgsvägen 12 • SE-441 43 ALINGSÅS • Sweden