Worth reminding people that your wicket-phonebook[1] demo's an example of Spring, as well as Hibernate/Ibatis?
Regarding Jetty, see [2]if anyone wants to go with Jetty6 rather than Jetty4. /Gwyn [1] - http://wicket-stuff.sourceforge.net/wicket-phonebook/ [2] - http://www.wicket-wiki.org.uk/wiki/index.php/Jetty6_testing On 14/06/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > not to mention the decorator pattern is used a lot in spring and for that > you also need interfaces. > > -Igor > > > > On 6/14/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote: > > > > > > > > On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote: > > > > > 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. > > > > 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. > > > > > > -Igor > > > > > > > > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
