On Dec 31, 2009, at 12:38 PM, Evgeny Ryabitskiy (JIRA) wrote:
To be honest I am still not sure that developing new container is better then using already created and well tested (for years) like Spring. Yes it's bigger but 300 kbs isn't so critical for huge application (my wars are 30 mbs)... at least not used classes are not loading to memory.
This is good point, and in fact we did evaluate this route. A benefit of our own container that outweighed everything else was that it is the most unassuming option. There will never be a conflict with the user application using a different version of Spring, etc. The fewer dependencies we have, the more self-containing cayenne-server.jar is, the easier it is for the end users to include Cayenne in their various environments (J2SE, JEE, OSGi, etc.) and various application stacks.
Even Cayenne 3.0 has too many dependencies to my liking. E.g. we are on Velocity 1.3, and the Velocity project is at 1.6.2 now. Apache Click uses Velocity for template rendering. So Click/Cayenne users will need to choose a single version of Velocity and pray that it works for both Cayenne and Click. So I sorta wanted to avoid this situation with DI.
Andrus
