Right, I agree spring, and especially when using custom spring namespaces, you can end up with lots of problems at startup time. FWIW, ActiveMQ (and Camel) can now be used with blueprint instead of spring-dm and that removes those problems ...
On Tue, Jun 29, 2010 at 10:27, Jeremias Maerki <[email protected]> wrote: > I was thinking about similar lines. So far, I didn't have much luck with > the features: either installs or uninstalls didn't work properly or I > was too lazy to write my own features. And I want more control over > which bundles are installed. So currently, I don't use features at all > although I'm a happy Karaf user. > > If I had some free time, I'd write a bundle that gets a directory which > has subdirectories with the bundle level as their name. It would set up > all bundles with the framework using the right start level. That sounds > just a bit like FileInstall but I would not include a directory poller. > > Example: > -- deploy > +-- 10 > +-- spring-core-2.5.6.jar > +-- spring-beans-2.5.6.jar etc. > +-- 20 > +-- activemq-core-5.3.0.jar > +-- activemq-pool-5.3.0.jar etc. > > Well, in a perfect OSGi world, bundle levels shouldn't be necessary but > reality shows problems with Spring and other bundles. > > On 29.06.2010 10:15:08 Charles Moulliard wrote: >> Hi, >> >> The existing Karaf platform uses two mechanism to deploy and start >> bundles at the launch of the Karaf server. Thes first one uses the >> bundles listed in the startup.properties file (+ bundle level) while >> the other is the provisioning mechanism based on feature file. >> >> It is possible to deploy "project" bundles at the startup of the Karaf >> but that means that they should be present in the default system >> repository (and listed in startup.properties file). To use another >> repository, the variable bundle.loacations must be set in the file >> config.properties. >> >> Personally, i think that the start up mechanism should be keep for the >> launch of Karaf and should not be used to start project bundles. They >> should be deployed and started through features mechanism >> >> Nevertheless, feature xml file does not define the bundle startup >> level. So I suggest that we add a new attribute to the description of >> the bundle/feature to define the bundle level ? >> >> What do you think about that ? >> >> KR, >> >> Charles Moulliard >> >> Senior Enterprise Architect (J2EE, .NET, SOA) >> Apache Camel - ServiceMix Committer >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Blog : http://cmoulliard.blogspot.com | Twitter : >> http://twitter.com/cmoulliard >> Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard > > > > > Jeremias Maerki > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
