Niclas,
Do you mind me forwarding this email to the ofbiz mailing list to get
others involved?
Many thanks,
Chris
On 6 Apr 2007, at 09:22, Niclas Hedhman wrote:
On Friday 06 April 2007 13:05, Christopher Snow wrote:
Apache ofbiz is an application that has it's own component (i.e.
bundle management system). There is interest in the ofbiz community
for migrating ofbiz to an OSGi approach but I don't know where to
start. Would this mailing list be able to offer help and guidance on
converting apache ofbiz to OSGi?
Definately,
can't say that I know your codebase very well, but somehow I got the
impression that it is already fairly modular.
You will first need to identify what your goals are.
Hard nuts to crack;
1. If you want reloadability of bundles in runtime, you need to think
in "Service" terms, and respect the service layer specification.
This means that you don't hold on to service instances, either by
dropping them after each use, or tracking their arrivals and
departure through the service tracker.
2. If you want to only want a limited part of the application to stop
during reloads, you probably need to break the API from the Impl
into two (or more) separate bundles. The API is stable, and won't
change often, and the API is the only one that exposes classes
to other bundles. But, the API can't reference the impl directly,
and you will end doing the service layer to solve that.
3. Deployment scenarios. OSGi is not primarily a web technology, and
is fairly intrusive on classloading. But people still wants to
deploy OSGi inside servlet containers. And there is a Servlet
Bridge developed by Simon Kaegi, I think hosted at Eclipse
Equinox, possible its Incubator/Sandbox. This component allows
the outer servlet's requests to be routed into the OSGi world
and its Http Service specification.
Cheers
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
