[
https://jira.jboss.org/jira/browse/JBMAN-28?page=com.atlassian.jira.plugi...
]
Scott M Stark resolved JBMAN-28.
--------------------------------
Resolution: Done
This end up being resolved as a side-effect of JBMAN-27 as the managed object for each
collection element is built based on the element value, and interfaces are now used to
resolved the InstanceClassFactory.
AbstractManagedObjectFactory.initManagedObject does not look into
collections for the property type
---------------------------------------------------------------------------------------------------
Key: JBMAN-28
URL:
https://jira.jboss.org/jira/browse/JBMAN-28
Project: JBoss Managed
Issue Type: Bug
Affects Versions: JBossMan.2.0.0.CR2
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossMan.2.0.0.CR3
When a ComponentDeployer like KernelDeploymentDeployer extends
AbstractComponentDeployer<KernelDeployment, BeanMetaData> is processed for its
ManagedObjects, recursion into the property that corresponds to the components
(List<BeanMetaData> beanFactories in this case) to build its ManagedObject fails to
pull out the BeanMetaData and map this to the registered InstanceClassFactory. The logic
for obtaining the InstanceClassFactory needs to deal with collections/arrays better.
--
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