]
Charles Crouch updated JBAS-6227:
---------------------------------
Fix Version/s: JBossAS-5.1.0.CR1
(was: JBossAS-5.1.0.GA)
Priority: Critical (was: Major)
Pushing back into the CR1 bucket and restoring its priority. I want to talk to emanuel
about what can still be achieved her for CR1. We can push to GA or not based on the
outcome of that discussion.
Only way to remove a managedcomponent is to remove its deployment
-----------------------------------------------------------------
Key: JBAS-6227
URL:
https://jira.jboss.org/jira/browse/JBAS-6227
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Charles Crouch
Assignee: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
Original Estimate: 1 week, 2 days
Remaining Estimate: 1 week, 2 days
Right now I'm using the following to remove a component:
ManagementView mgtView = ProfileServiceFactory.getCurrentProfileView();
ManagedComponent managedComponent = getManagedComponent();
ManagedDeployment deployment = managedComponent.getDeployment();
mgtView.removeDeployment(deployment.getName(),
ManagedDeployment.DeploymentPhase.APPLICATION);
mgtView.process();
But if you have other things defined in the deployment, e.g. the hsqldb-ds.xml deployment
contains jboss:service=Hypersonic,database=localDB service as well as the datasource, you
end up blowing the whole lot away.
There is an api on the deployment which *looks* like it would help, but replacing:
mgtView.removeDeployment(deployment.getName(),
ManagedDeployment.DeploymentPhase.APPLICATION);
with
deployment.removeComponent(managedComponent.getName());
appears to remove nothing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: