[
https://jira.jboss.org/jira/browse/JBDEPLOY-99?page=com.atlassian.jira.pl...
]
Adrian Brock closed JBDEPLOY-99.
--------------------------------
Fix Version/s: JBDEPLOY-2.2.0.Alpha
Resolution: Done
This has been done.
Each deployment/subdeployment/component is now registered with the MBeanServer
if the DeployersImpl has been and the "registerMBeans" property is true (the
default).
There is a new interface DeploymentMBean that a DeploymentContext needs to
implement to take part in this behaviour.
Additionally, so we can maintain/query which Deployers are modifying attachments,
there is a new DeployerTracker helper class that has a getCurrentDeployer()
method. Its stack of deployers is maintained by the DeployerWrapper class.
A new TrackingMutableAttachments wrapper is used to monitor attachment changes
so that the actual attachments implementation can be changed as required
without having to know about these details.
Add some mangement operations so you can query deployment flows
---------------------------------------------------------------
Key: JBDEPLOY-99
URL:
https://jira.jboss.org/jira/browse/JBDEPLOY-99
Project: JBoss Deployers
Issue Type: Task
Components: core
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBDEPLOY-2.0.0.CR2, JBDEPLOY-2.2.0.Alpha
There should be some management operations so you can see what deployers
are involved in a particular deployment flow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira