RE: [Springframework-developer] AOP

[Kopylenko, D. <dko...@ac...>]

Yes, Rutgers University indeed. And for now we're are pretty happy about
current aop implementation/ease of use.

Regards,
Dmitriy.

-----Original Message-----
From: rod...@in... [mailto:rod...@in...]
Sent: Friday, May 23, 2003 09:38 AM
To: Kopylenko, Dmitry
Cc: 'spring-dev-list'
Subject: Re: [Springframework-developer] AOP


<dmitry>
Rod, everyone,

I just want to report that we've started to use AOP framework 
for one of our
big web app. projects. 

Also, here is the list of Spring components/sub-frameworks 
we're using for
this project:

* BeanFactory
* WebApplicationContext
* JDBC
* Tx infrastructure (via declarative aop approach)
* MVC web framework
* AOP

Regards,
Dmitriy.
</dmitry>

Good to hear this: thanks for letting us know. I assume you 
mean Rutgers University? It would be great to have a list of 
reference sites before we release 1.0.

I'm also very excited about AOP. 

I'm done with changes to AOP stuff for 0.8. Beyond that, I'm 
keen to progress with better support for transaction and 
other attributes, including source-level attributes.

As you progress with your project, it would be great to hear 
any suggestions you may have about how to improve Spring AOP 
and make it easier to use. If you're entirely happy, that's 
useful feedback too!

Unfortunately it appears that Jon Tirsen (Nanning) won't 
commit to supporting the AOP Alliance interfaces--which he 
was heavily involved in defining--until the AOP Alliance "has 
more momentum." I find this a disappointing copout, but I 
think the problem is partly that he simply doesn't have time 
to make the changes, which would impact his use of Nanning in 
his day job. (It would be hard to justify the cost to his 
employers.) So unfortunately I don't think the AOP 
Alliance/interoperability is going to be a reality any time 
soon. However, it does mean that not only is Spring unique in 
the AOP space as a complete, integrated, solution (just drop 
in AOP if you want to use it), but is the only AOP solution I 
know of that has made a genuine effort to comply with an open 
API.

As Spring is the only implementation of the AOP Alliance 
interfaces for the moment, if anyone has any strong feelings 
that anything should be changed about those interfaces, this 
list is probably the best place to discuss it. I'm fairly 
happy with them for now. I will have to comment them properly 
before 1.0. And put Javadoc on AOP Alliance SF.

Regards,
Rod