Duane Yang wrote:
we can modify the configuration of the application through a management console. And if I reboot the server, the changes to the configuration won't be lost.
However on JBoss, on server's reboot, the application will be undeployed and deployed again, and the changes to the configuration though the management console are lost.
Is that some custom management console? If yes, can you provide the details about where it stores those changed configurations? And is your application deployed as an archive or in exploded (folder) format? And which version of JBoss AS are you using?
Thanks for your help. The console is the Oracle Enterprise Manager. The configurations are stored in a LDAP server. We have application authorization policies (in a file named jazn-data.xml) packaged in our applications. The application policies will be migrated to the central policy store (on the LDAP server) on deployment and removed from the central policy store on undeployment. We created a custom deployer, which extends org.jboss.deployers.spi.deployer.helpers.AbstractDeployer and implements its deploy and undeploy methods, so that application policy can be migrated to the central policy store on deployment and be cleaned from the centrol policy store on undeployment. Our problem can also be resolved if AbstractDeployer can distinguish between normal deployment/undeployment and deployment/undeployment on JBoss' startup/shutdown. Is that possible?
Our apps are usually deployed as archives but can also be deployed in exploded format. We are using jboss-5.1.0.GA.
Is that possible to detect whether current status of JBoss is "starting up"/"shuting down"?