The focus these days are to simplify frameworks, for instance take guice and warp persist. Really really simple to use and to setup. Spring has a bit to learn about java configuration from these guys (I last time I tried spring was in 2.5) however I've only tried guice 1.0.
If it takes 1 day to utilize a framework that can find a whale, it's probably wort the effort. On the other hand if it requires 50% of the project plan, it's probably not. pro's with guice are: plain java (no need for extra tools, just like wicket), refactor safe, KISS, and works like I thought it would:) cons: a little more intrusive since configuration are in java, although very simple to extend to property files or db (it's just java) pros with spring: huge framework (you think of something, they probably got it somewhere), less intrusive cons: xml based, huge framework.. Anyhow both frameworks go nicely with mocking etc... my 2 cents. 2009/6/9 Martin Makundi <[email protected]>: >> Ok, I think we can just agree to disagree, but will you do me a favor? >> When (not if) you encounter a situation like Martijn is talking >> about, will you post back to the list? > > I just believe in principle that hunting for some bug for 3 weeks is > much less waste than dragging some toolkit along for 3 years, 6-man > team, 100-man team, however big the more waste. Usually only few > people hunt for the bug for 3 weeks. > > And it is true, it is important to know what to do yourself and what not to. > > ** > Martin > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
