Thanks for the quick reply.</div>
</div>
I already tried to use this extension point for my purposes: I wrote the attached prerequisite bundle launcher that is triggered by the IStartup extension point. It installs several bundle trackers that start the required bundles just when they get available.</div>
</div>
This solution did not work on all machines. In some cases, it always worked, on other machines it always failed. I assume this is due to varying bundle start order over different installations (which might be governed by directory order or file timestamps).</div>
</div>
The IStartup solution works fine for application bundles that just install prerequisite services, but it does not work reliably for basic infrastructure bundles or framework components like DS and EclipseLink. These bundles have to be started really early, and IStartup does not use start levels.</div>
</div>
For such cases, I suggest to introduce dots-specific properties for use in config.ini that can be used to fine-tune the dots environment:</div>
-
javaddin.additional.bundles allows you to specify bundles along with their start levels. Its content get appended to osgi.bundles by the launcher.
-
javaddin.clean (boolean) that allows you to suppress workspace cleanup, thus allowing a persistent manual configuration.
javaddin.clean (boolean) that allows you to suppress workspace cleanup, thus allowing a persistent manual configuration.Thanks for the quick reply.
I already tried to use this extension point for my purposes: I wrote the attached prerequisite bundle launcher that is triggered by the IStartup extension point. It installs several bundle trackers that start the required bundles just when they get available.
This solution did not work on all machines. In some cases, it always worked, on other machines it always failed. I assume this is due to varying bundle start order over different installations (which might be governed by directory order or file timestamps).
The IStartup solution works fine for application bundles that just install prerequisite services, but it does not work reliably for basic infrastructure bundles or framework components like DS and EclipseLink. These bundles have to be started really early, and IStartup does not use start levels.
For such cases, I suggest to introduce dots-specific properties for use in config.ini that can be used to fine-tune the dots environment:
javaddin.additional.bundles allows you to specify bundles along with their start levels. Its content get appended to osgi.bundles by the launcher.
javaddin.clean (boolean) that allows you to suppress workspace cleanup, thus allowing a persistent manual configuration.