We're updating the issue view to help you get more done. 

WebSphere container: allow to set classloading strategy for deployments


Sometimes it is useful to configure the classloading strategy for the deployment to PARENT_LAST instead of the default one PARENT_FIRST.

This is needed for example when the deployment is using some artifact (jar) that also comes by default from the WebSphere, but in older version, thus some fields/classes may be missing and the deployment then fails.

I would like to implement this as a contribution to the Cargo project.
It should be fairly easy to do this using the wsadmin directly when deploying the application (e.g. war). However, I am struggling a bit with how to make this configurable. This setting is specific to a deployment and may be different for different deployments, so configuring this on the container level may not be the best idea (although it would probably be OK in most cases).
I guess the solution would be to add some configuration option directly to the deployable, but I could not find how to do that.

My knowledge of the Cargo internals is very limited, so it would be great to have some feedback from the developers on what is the best approach how to implement this.

Note: Configuring the classloader is described in detail here: http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.nd.doc/ae/txml_classloader.html



Petr Široký


Petr Široký


Fix versions