+1
On Nov 8, 2009, at 5:21 AM, Dennis Reedy wrote:
On Nov 8, 2009, at 1251AM, Peter Firmstone wrote:
I had avoided OSGi purely due to the controversy it generates on
this list, however without the Service Pattern one cannot upgrade a
package without first persisting everything and shutting down the
entire JVM, then restarting. At least OSGi allows you to stop a
bundle and any dependents, persist what you need to then start with
a later bundle version if desired, without having to persist or
shut down the entire JVM.
If thats all you want you dont need OSGi. Service lifecycles are
supported with a variety of container approaches, from JEE, Spring
to Rio. You also do not need to shutdown the JVM to load new service
classes.
Adopting OSGi as a micro-kernel architecture for wiring up services
inside the JVM is a different thing. Looking at distributed OSGi is
a totally different thing on top of that. IMO, if you want to
consider OSGi for River, you focus on the former, not the latter.
Mike McGrady
Principal Investigator AF081-028 AFRL SBIR
Senior Engineer
Topia Technology, Inc.
1.253.720.3365
[email protected]
