Re: [Springframework-developer] API simplification

[Ken K. <kk...@kk...>]

Rod,

I have some reservations about your proposed deletions. I've been 
considering a non-J2EE Spring project that would need to use property 
change listeners and am not sure about going down the AOP route for 
this. The FactoryBean  "pass- through" properties support also sounds 
useful for this project. Sorry I can't be more certain about needing 
these features at this time as I just don't have the time right now to 
look into it more deeply.

BTW, got any good reading material recommendations for getting  started 
with AOP ?

Regards,
Ken


>I've done the package rename and will commit it to a
>	new "spring" module tonight.
>	
>	I'll post more details when I'm done.
>	
>	I've been considering some potential simplifications. I hate
>	dead code--it adds bloat and makes frameworks harder to use.
>	(I've just been working with TopLink...) As we progress to
>	1.0 it's a good opportunity to cut back to the
>	essentials...it will be hard to remove anything (however
>	useless) afterwards.
>	
>	As a start, I'm considering removing the JavaBean event
>	support from BeanWrapper. I've not used it in any
>	applications. Has anyone else used it?
>	
>	Now Spring has AOP support, it's possible to add listeners to
>	property change events using interceptors, rather than this
>	rather kludgy part of the JavaBeans API.
>	
>	Removing event support would get rid of about 150 lines of
>	code in the beans package, and simplify the API for users.
>	
>	Any thoughts on this?
>	
>	Another candidate on my potential hitlist is the "pass-
>	through" properties support for FactoryBeans. I've not seen a
>	need to use this in practice (although I implemented it).
>	
>	Regards,
>	Rod
>	
>  
>