I have a rather complicated OSGi application that uses Declarative Services and is intended to be deployed to Equinox. The challenge now is to make this application deployable in WAS 8.
The first attempt was quite pragmatic: I deployed an EAR that started basically the same Equinox, and after some tricks of the WAS boot policy it worked.
Now I want to go further: get rid of the Equinox runtime and deploy my packages “natively” in WAS 8. Therefore, I compiled an EBA consisting of my business packages, their dependencies and the Equinox DS runtime. The EBA is deployed as an asset and integrated into the BLA. The application even started and starts, but the components are not initialized.
The point is that you need to run equinox.ds in front of your own business packages (UPDATE: optional, s. Discussion below) to get DS to do its job. But how can I talk about packages that should be run first in a deployed EBA? I need some analogue of the config.ini Equinox file.
I know that I can reinstall my components using a supported Blueprint, but frankly, this is the last thing I would like to do. It should be possible to make Equinox DS work, right?
Another question: how to get the OSGi console for one native application deployed under WAS 8? I want to control my packages, but there seems to be no way to do this from the management console.
UPDATE
Thanks to BJ and Neil (see discussion below), the question boils down to "How do I create a specific package in my own OSGi application deployed in WAS 8.0?"
source
share