If it's not possible to do it declaratively in jboss 5.1, what should I implement (is there any tutorial how to do it)?
This is how we handle things in Deployers 2.2.x
Where jboss-classloading-domain.xml is parsed into ClassLoadingDomainMetaData.
You probably need to do something similar.
Thanks for quick response.
I'm new to the jboss and deployers concepts so I would need some more help with this.
Does it mean that I should
1] implement my own deployer according to AbstractClassLoadingDomainDeployer.java (implemented in 2.2)
2] compile it with jboss-deployers package 2.0.7
3] put it to the jboss 5.1 [jboss]/server/default/deployers/myweb.deployer
4] configure myweb.deployer somehow (I really don't know how. I haven't found any docs about creating deployers)
5] configure jboss or my web application to use myweb.deployer
Please excuse me if I misunderstood something.
I have some additional questions:
* Shall the myweb.deployer replace original jbossweb.deployer, or could it be used just my web application? I would like to minimalize influence on the other deployed applications.
* Code of AbstractClassLoadingDomainDeployer doesn't filter any loaded resources itself, so is the configuration in jboss-classloading-domain.xml sufficient?
Does it mean that I should ...
I would simply add a new custom deployer and handle this things programatically only for your app.
e.g. recognize your app either by name or some marker resource