[
http://jira.jboss.com/jira/browse/JBMICROCONT-166?page=comments#action_12... ]
Adrian Brock commented on JBMICROCONT-166:
------------------------------------------
This has been fixed by
1) Automatically create aliases for the canonical name when the context has a name that
looks like a JMX ObjectName but it is not already in canonical form
2) Applied the same ObjectName fix to AbstractDependencyItem.setIDependOn()
This is a generic fix in the AbstractController[Context].
Still to write some tests for the different dependency types in the kernel/pojo project.
Although, I'm not convinced that non-direct dependencies like Demand should have this
applied directly.
However, the above fix (part 2) does apply it to whatever the Demand dependency resolves
to.
If bean name, dependency, demands, supplies looks like an object
name, the register its canonical form
------------------------------------------------------------------------------------------------------
Key: JBMICROCONT-166
URL:
http://jira.jboss.com/jira/browse/JBMICROCONT-166
Project: JBoss MicroContainer
Issue Type: Feature Request
Components: Dependency
Affects Versions: JBossMC_2_0_0 Beta3
Reporter: Bill Burke
Assigned To: Adrian Brock
Priority: Critical
Fix For: JBossMC_2_0_0_CR1
See forum reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira