Re: AspectJ and the Plexus core

Hi,

I just wanted to note that I think this runtime AspectJ stuff is
very cool and would be a prime reason for convincing the company I'm
currently working for for moving one of their applications into a
container environment (something I've been looking forward to for
awhile now).

The idea I have of how I'd like to use the runtime AOP features is
to have introductions dynamically plugin modules into the system.

E.g. instead of having one huge domain model with every possible
feature and then just flip them on and off by setting admin-level
boolean variables, have each module be its own service that could
then introduce itself to the other services.

E.g. the core user object has just the basics:

 user.name
 user.address

But then after the accounting module is enabled in the config, one
of it aspects runs and introduces into the user class:

 user.accounts
 user.amountDue

Or what not.

Is this the kind of use case you're hoping AOP-enabled Plexus could
solve? Or am I mis-understanding what you're trying to do?

(As an aside, I have a lot of respect for the skills of people on
this list, so if you have a bad gut reaction to my proposed
architecture of AOP-introducted features, I'd appreciate it if you
could say as much, even without a detailed explanation of why you
think so).

Thanks,
Stephen