Why Don't They Do Bundles This Way Instead? [message #545918] |
Fri, 09 July 2010 15:25 |
Wm. Bainbridge Messages: 6 Registered: April 2010 |
Junior Member |
|
|
One of the big problems I ran into with multiple complex apps running in dmServer was that different open source packages, such as Hibernate, ActiveMQ, CXF and so on, have some overlapping package dependencies, that are sometimes incompatible with one another. So all these packages have a ton of import-package statements that make it absolute hell trying to figure out how to provision the container so that everything loads and works right. So, why don't the people who put together the project bundles start importing bundles instead of packages? If all these bundles are designed to run in an OSGi container, and the deployment unit in OSGi containers is bundles, wouldn't it be way simpler to make the dependencies available as bundles and import those bundles, rather than importing packages that might be available in several different bundles in an active, enterprise OSGi container? Just wondering.
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07242 seconds