Using WebSphere 8.5, we've created a shared library, set to use an isolated class loader. In the Admin console, we can associate this shared library with our application and confirm that it the jars in the shared library are in effect. But whenever the application is redeployed, the association is lost.
We'd like to adjust the Manifest.MF, or a deployment descriptor, to reference the shared library so that the application can be redeployed without needing to reset the association in the Admin console. We're unable to make sense of the WebSphere documentation around this. Does anyone have an example of how to make this association?