Re: [Springframework-developer] aop jar

[<rod...@in...>]

We need to review the whole distribution Jar thing. 

The AOP framework is fairly small and, I think, part of the 
core. (Not so for the interceptors.)

I'm inclining towards emphasising a single Jar--the "full" 
Jar at present. Simply including this in a web app will do 
the job. At a bit over 400K it's not too large, compared to 
many other libraries.

The only problem is that in EJB deployment this may produce 
nasty gotchas when the EJB loader is the parent of the WAR 
loader. In the release with the book I took care to package 
around this issue: I think it's likely Spring in its current 
form would pose more problems.

Personally I see part of Spring's value in that it provides a 
lighter-weight alternative to EJB for many things. However, 
some users will need to use Spring with EJB, and we need to 
support this.

Any thoughts on this?

Regards,
Rod