On Jul 15, 2007, at 8:03 PM, Alex Karasulu wrote:
Here's that thread on discussing the CiDIT agenda. Let's take a look at the following
link before beginning:
Yikes, I'm afraid this will take 6 months to a year to do, and unless you write "jdo for ldap", including an enhancer, I think its' going to be pretty painful to add new configuration elements.
Someone suggested a while back that we avoid the "jdo for ldap" problem by just storing server.xml in ldap as text. IIUC this could be done in a couple of days. Exactly how much really useful functionality would this lose compared to the fine grained approach?
What if each component/bean configuration were stored as xml text separately, each with a (unique) name, and the links were determined by the names?
BTW, unless you write a fancy dependency tracking system (i.e. the geronimo kernel) I think that any change basically requires stopping and restarting the server, so I'm not sure there is really much advantage to splitting up each bean separately.
And finally, why are there all these configuration objects that spring creates that then go and create the actual runtime objects, rather than having spring create the runtime object directly? In particular, why is there an interceptor configuration object rather than just interceptors?
Are you finding that Spring has some limitations that you are running into? Otherwise why eliminate it?