not wishing to get in the way of positive vibes (+1 to positive vibes), but to me the use cases mentioned so far sound like a rather 'straightforward' requirement for rather straightforward AOP. Check out (google for)

* nanning
* aspectwerkz
* aop alliance
* hivemind
* jboss interceptors
* nanocontainer AND aop
* containerkit
* xinvoke
* geronimo
* tomcat
* ....

and that's just a top-of-head list of a part of the dozens of mutually incompatible AOP/interceptor/pipeline frameworks out there; a new one seems to pop up every month. This is not a very nice situation. Adding another one seems like a bad idea. The AOP alliance is specifically about digesting the common ground 'n stuff, it might be a good place to start.

Alex Karasulu wrote:
So where do you want to do this?

AOP Alliance?


I won't do something as silly as to actually block the development of an interceptor framework over here, but I do think its a bad idea. Collaboration++, you know :D

--
cheers,

- Leo Simons

-----------------------------------------------------------------------
Weblog              -- http://leosimons.com/
IoC Component Glue  -- http://jicarilla.org/
Articles & Opinions -- http://articles.leosimons.com/
-----------------------------------------------------------------------
"We started off trying to set up a small anarchist community, but
 people wouldn't obey the rules."
                                                        -- Alan Bennett



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to