Hello Karl, thanks for your help. That is exactly what I was looking for. I even wonder why this option is not used in the Felix config.properties to specify the default auto start bundles, i.e.
felix.auto.start.1= \ reference:file:bundle/org.apache.felix.shell-1.0.1.jar \ reference:file:bundle/org.apache.felix.shell.tui-1.0.1.jar \ reference:file:bundle/org.apache.felix.bundlerepository-1.0.3.jar However, the problem with multiple instances remains. Are there any known best pratices to resolve this issue. A solution like java -Dfelix.cache.profile=%USERPROFILE%/myApp/%CURRENTTIMEMILLIS% -jar %FELIX_HOME%/bin/felix.jar (where CURRENTTIMEMILLIS is the current start time used to distiguish mutliple instances) is somewhat cumbersome and causes new problems, e.g. how to get rid of obsolete profile instances, record bundle state changes, etc. Another question is whether it is possible to (programmatically) detect that a profile is already in use, which would at least allow to reject multiple invocations by a single user. Regards Robert Karl Pauls wrote: > > I think what you need is the "reference:" prefix. If you install a > bundle using a url that starts with "reference:" (e.g., > reference:file:foo.jar) then the jar is not copied into the cache. So > what you want to do is to put all the shared bundles in one dir and > install them by reference into the different profiles. You can not > however, share profiles between instances (that will mess-up things). > > Hope this helps? > > regards, > > Karl > > On Wed, Jun 25, 2008 at 2:53 PM, meinc <[EMAIL PROTECTED]> wrote: >> >> Hi all, >> >> I need some help and advice on deployment of felix based desktop >> applications. >> We intend to use felix for a typical swing desktop application which is >> installed on a single computer for multiple users. Even a single user may >> start the apllication more than once. >> >> 1.) Would it be save to share a single felix cache profiledir for several >> instances of the application >> >> I already tested to share the profile and it seems to work. However since >> the cache does not distinct between bundle install and bundle state >> locations I'm afraid of blocking write operations that reflect state >> changes >> >> 2.) Is it reasonable to distribute a preconfigured felix cache profiledir >> rather distribute the bundles and let felix do the initial cache setup. >> >> I'm asking these questions since we have to integrate a third party >> archive >> which has a size of about 80 MB and we don't want this OSGified jar >> copied >> to multiple profiles. >> >> Regards >> Robert >> -- >> View this message in context: >> http://www.nabble.com/Deployment-and-Profile-usage-for-multi-user-environments-tp18111719p18111719.html >> Sent from the Apache Felix - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > -- > Karl Pauls > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Deployment-and-Profile-usage-for-multi-user-environments-tp18111719p18113313.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
