Spring is mostly static. That is one of the problems with our current Spring-only implementation - it can't be modified at runtime. That's where OSGi comes in. :).
Spring allows us to take the wiring out of the code and make it more accessible. I can change Hibernate's DataSource without rebuilding the entire bundle. In our current system, all of the Spring files are contained in a standard filesystem directory, so editing is easy. In this solution I'll have to modify the bundle jar to edit a Spring file, but it still keeps me from having to rebuild the bundle's code. -Jeremy On 9/29/05, Marcel Offermans <[EMAIL PROTECTED]> wrote: > Enrique Rodriguez wrote: > > > Jeremy Volkman wrote: > > > >> Any questions/comments/suggestions are greatly appreciated. :) > > > > > > Can bundles still be added and removed at runtime? Your write-up > > makes it sound like the metadata is "centralized" in a single Spring > > xml config and therefore doesn't come and go with the bundles. > > He is talking about Spring XML files (plural). I'm not very familiar > with Spring. Does it allow dynamically adding and updating "components" > like OSGi? Or is it more like a web application, defined once and fairly > static from that point on? > > It is interesting to see others considering OSGi for these types of > enterprise systems, since we've had similar talks with a customer about > this. > > Greetings, Marcel > >
