Best practices in OSGi bundle management during development [message #12947] |
Mon, 29 September 2008 09:30 |
|
I asked more or less this same question on the equinox group but did
not get a reply, so I thought I would try again here.
My experience is that it takes a lot of manual intervention to sort out
dependencies when doing RCP development and with OSGi server side it is
even more difficult. I would be interested in the experiences of other
developers on how you tackle this. Also how do you go about trimming
the bundle list to the minimal required to reduced the foot print? Has
any one found a reasonable way to automate the process?
Btw, I have Googled this and have come up surprisingly empty handed.
Are these not concerns in the community today? Any pointers to
materials I have missed would be greatly appreciated.
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme & ORMF
|) ::: (| Open Requirements Management Framework
====w=w==== [http://www.eclipse.org/ormf/]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
Re: Best practices in OSGi bundle management during development [message #12976 is a reply to message #12947] |
Mon, 29 September 2008 10:16 |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Joel Rosi-Schwartz schrieb:
> I asked more or less this same question on the equinox group but did not
> get a reply, so I thought I would try again here.
>
> My experience is that it takes a lot of manual intervention to sort out
> dependencies when doing RCP development and with OSGi server side it is
> even more difficult. I would be interested in the experiences of other
> developers on how you tackle this. Also how do you go about trimming the
> bundle list to the minimal required to reduced the foot print? Has any
> one found a reasonable way to automate the process?
>
> Btw, I have Googled this and have come up surprisingly empty handed. Are
> these not concerns in the community today? Any pointers to materials I
> have missed would be greatly appreciated.
>
> Thanks,
> Joel
Joel,
this is the hard part of OSGI development today.
you get some help from PDE to watch or analyze dependencies
but (from my experiences) it will take some time to get the right
tooling for OSGI - bundle - development
at the moment its hard enough to combine some things,
say eclipse rcp + equinox + riena + easybeans + hibernate + ...
you're in luck, if all are using package-import for common used
bundles instead of required bundles.
you're again in luck if versioning is well done _ so it could happen
that one exports a package without version number and another one
imports with version - then the only way is to rebundle it by yourself
next point is that many bundles can do the same task (per example
export log4j) but you have to choose where to get this common bundle:
from eclipse, springsource or bundle it by yourself
if you look at the hard work from SpringSourceEnterpriseBundle
repository, then you'll see what you have to watch to get the
dependencies resolved
at the moment its a hard work and sure mainly manual work of the
OSGI app architect to decide which bundles to combine, which to
re-bundle and which to self-bundle.
then inside your project you can try to automate as much as possible
only my 2c
ekke
btw: some of my experiences and rules:
http://ekkes-corner.blogspot.com/2008/09/pde-and-3rdparty-bu ndles-in-osgi.html
|
|
|
Re: Best practices in OSGi bundle management during development [message #575414 is a reply to message #12947] |
Mon, 29 September 2008 10:16 |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
Joel Rosi-Schwartz schrieb:
> I asked more or less this same question on the equinox group but did not
> get a reply, so I thought I would try again here.
>
> My experience is that it takes a lot of manual intervention to sort out
> dependencies when doing RCP development and with OSGi server side it is
> even more difficult. I would be interested in the experiences of other
> developers on how you tackle this. Also how do you go about trimming the
> bundle list to the minimal required to reduced the foot print? Has any
> one found a reasonable way to automate the process?
>
> Btw, I have Googled this and have come up surprisingly empty handed. Are
> these not concerns in the community today? Any pointers to materials I
> have missed would be greatly appreciated.
>
> Thanks,
> Joel
Joel,
this is the hard part of OSGI development today.
you get some help from PDE to watch or analyze dependencies
but (from my experiences) it will take some time to get the right
tooling for OSGI - bundle - development
at the moment its hard enough to combine some things,
say eclipse rcp + equinox + riena + easybeans + hibernate + ...
you're in luck, if all are using package-import for common used
bundles instead of required bundles.
you're again in luck if versioning is well done _ so it could happen
that one exports a package without version number and another one
imports with version - then the only way is to rebundle it by yourself
next point is that many bundles can do the same task (per example
export log4j) but you have to choose where to get this common bundle:
from eclipse, springsource or bundle it by yourself
if you look at the hard work from SpringSourceEnterpriseBundle
repository, then you'll see what you have to watch to get the
dependencies resolved
at the moment its a hard work and sure mainly manual work of the
OSGI app architect to decide which bundles to combine, which to
re-bundle and which to self-bundle.
then inside your project you can try to automate as much as possible
only my 2c
ekke
btw: some of my experiences and rules:
http://ekkes-corner.blogspot.com/2008/09/pde-and-3rdparty-bu ndles-in-osgi.html
|
|
|
Powered by
FUDForum. Page generated in 0.01972 seconds