Just a follow up on this for the record. I got HASingletonDeploymentScanner to work with
the repository based profile service as well, well enough at least for AS 5 CR1.
Basically, the HASingletonDeploymentScanner has the ProfileService and the MainDeployer
injected. When the ProfileService is injected, it checks if it exposes a
DeploymentManager. If yes, when it becomes master or stops being master it
deploys/undeploys content via the DeploymentManager API (distibute, getRepositoryNames,
start, stop, undeploy). The getRepositoryNames() method Scott added yesterday was most
helpful. :)
If no DeploymentManager (i.e. the basic profile service) it deploys/undeploys by calling
add/removeDeployment on the ProfileService and the MainDeployer and then tells the
MainDeployer to process().
That's a temporary solution, but restores the feature, has educated Brian, and means
there's now at least a unit test of deploy-hasingleton; never was one before.
http://jira.jboss.com/jira/browse/JBAS-5682
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161194#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...