On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
this is a common misconception, you do not need to use interfaces for everything. spring handles beans not backed by interface via cglib when they need to be proxied for aop/transactions.
a good portion of things you declare in the spring container are the things that are going to vary from deployment to deployment - and for those things you need to have an interface that is backed by multiple implementations, otherwise it wont work. likewise in spring code itself there are multiple implementations for most things - that is why the spring code has a lot of interfaces.
I guess I avoid it because it appears to force you into thinking in an
IoC way and I don't like the idea of configuring my classes w/ XML and
using interfaces for *everything* - sometimes that's just more complex
than the problem at hand.
this is a common misconception, you do not need to use interfaces for everything. spring handles beans not backed by interface via cglib when they need to be proxied for aop/transactions.
-Igor
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
