The special outliner is really just the Java outline view. Under AJDT
it will show AspectJ constructs. You will need to do a full recompile
to see an accurate structure outline for all the files. (The
incremental compile will not update the outline view properly.)
Cheers,
Nick
On Jul 9, 2004, at 1:30 PM, Warner Onstine wrote:
Thanks all,
Decided on AspectJ due to several issues, with Eclipse 3 and AJDT
things are pretty slick. However I'm still not seeing the special
outliner that I've seen screen shots of, any ideas on why that is?
Note - I did turn on incremental compile, issues with that?
-warner
On Jul 6, 2004, at 9:30 PM, Nicholas Lesiecki wrote:
Hi Warner,
Naturally I've used AspectJ. I think it offers the most power and
expressiveness, though I have heard good things about Spring if all
you want is declarative transaction management (I spoke to Drew today
who sang its praises).
VMS is using AspectJ full bore to manage a variety of application
level concerns in our Adbase project. One of the hottest areas of
development right now is enhancing Hibernate by adding many of the
features we miss from EJB (automatic enlistment of new objects with
the Session, bidirectional relationship completion). We've also used
it make unit testing a lot easier. The reaction of the team has been
surprisingly positive. We've been able to achieve a lot with a few
simple aspects, and all of the developers I've used it with have
gotten up to speed quickly.
If you (or anyone else on the JUG list) has any questions about
AspectJ, I'll do my best to answer them--either here or on the
aspectj-users list. I'm also available for some consulting if you
need help through a rough patch.
Oh, BTW, I believe the Enterprise AOP presentation at this link has
some good sample security code:
http://newaspects.com/presentations/
Best of luck with AOP,
Nick
On Jul 6, 2004, at 12:27 PM, Warner Onstine wrote:
Hi all,
I am trying to figure out what the best solution is for implementing
aspects with a framework like struts. I don't have any constraints
(so far), but I have investigated using the following:
Spring AOP - won't manage anything but the beans, but neat if that's
all you're going for
AspectJ - need to compile your aspects into the code
AspectWerkz - need to specially configure the run-time, or compile
your aspects into your code, I think it still uses xml for
configuration
Nanning - uses beanshell instead of xml
Dynaop - Need to create special proxy instances whenever you need
access to your class (and I don't know how I would integrate it with
Struts actions)
Basically what we need to immediately control with aspects are
security and logging.
Has anyone good experiences with this kind of AOP?
-warner
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Nicholas Lesiecki
Software Craftsman, specializing in J2EE,
Agile Methods, and aspect-oriented programming
Books:
* Mastering AspectJ: http://tinyurl.com/66vf
* Java Tools for Extreme Programming: http://tinyurl.com/66vt
Articles on AspectJ:
* http://tinyurl.com/66vu and http://tinyurl.com/66vv
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Nicholas Lesiecki
Software Craftsman, specializing in J2EE,
Agile Methods, and aspect-oriented programming
Books:
* Mastering AspectJ: http://tinyurl.com/66vf
* Java Tools for Extreme Programming: http://tinyurl.com/66vt
Articles on AspectJ:
* http://tinyurl.com/66vu and http://tinyurl.com/66vv
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
