CDIBeanManagerJNDIDeployer should only bind the BeanManager for top level deployments
-------------------------------------------------------------------------------------
Key: SWITCHYARD-317
URL:
https://issues.jboss.org/browse/SWITCHYARD-317
Project: SwitchYard
Issue Type: Bug
Components: component-bean
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 0.2
I noticed this when deploying the camel-jms-binding quickstart, which contains a
hornetq-jms.xml file. What was happening was that the BindingVisitor was getting called
for the quickstart jar and also for the hornetq-jms.xml file that exist inside the
toplevel deployment.
Adding a check and only performing the binding if the deployment unit is a top level
deployment should fix the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira