Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread Christopher Arnold
I'm attempting to hot deploy a Camel route using the ActiveMQComponent into Karaf via the deploy folder using a blueprint xml file but I'm running into dependency issues. When Karaf attempts to start the created bundle I see this error: 2014-01-22 13:41:51,092 | ERROR | -SNAPSHOT/deploy |

Re: Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread Jean-Baptiste Onofré
By the way, I guess that it works with you install your route bundle using bundle:install ? The issue occurs only when dropping the file into the deploy folder ? Regards JB On 01/23/2014 03:21 PM, Jean-Baptiste Onofré wrote: Hi Christopher, what's the list of installed features ? Regards JB

Re: Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread Jean-Baptiste Onofré
Hi Christopher, what's the list of installed features ? Regards JB On 01/23/2014 03:07 PM, Christopher Arnold wrote: I'm attempting to hot deploy a Camel route using the ActiveMQComponent into Karaf via the deploy folder using a blueprint xml file but I'm running into dependency issues. When

Re: Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread A. Rothman
A wild guess here, but maybe it's the same issue with the ActiveMQ webconsole bundle as in https://issues.apache.org/jira/browse/AMQ-4850. If you're not using the ActiveMQ web console, try uninstalling it or installing the -noweb feature instead of the full feature, that solved all the

Re: Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread Jean-Baptiste Onofré
Good point: indeed I would install activemq-broker-noweb instead of activemq-broker. More over, AFAIR, the default activemq-broker feature installs a activemq.xml (in etc) including a JAAS plugin for authentication. I would try to remove the JAAS plugin. Regards JB On 01/23/2014 03:37 PM,

Re: Fwd: Deploy issues in Karaf/Blueprint

2014-01-23 Thread Christopher Arnold
Looks like this is at least related. I removed the activemq-web-console feature and that seems to get things working. Looking at bundle:tree-show it looks like for some reason the activemq-web-console is exporting all of the activemq packages and thus is getting wired to my bundle instead of