]
Scott M Stark resolved JBDEPLOY-132.
------------------------------------
Resolution: Done
DefaultManagedObjectCreator should pass in the attachment name as the
MO name
-----------------------------------------------------------------------------
Key: JBDEPLOY-132
URL:
https://jira.jboss.org/jira/browse/JBDEPLOY-132
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.0.CR5
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBDEPLOY-2.0.0.GA
The DefaultManagedObjectCreator is currently obtaining the attachment names for a
deployment, and then creating the ManagedObjects for them, passing in just the instance,
but not the name. This can lead to duplicate attachments in the case of an interface being
used as the attachment name as is the case for KernelDeployment. The problem is that the
default ManagedObject name is taken from the attachment.getClass().getName(), but this
would never be the interface name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: