[
https://issues.apache.org/jira/browse/AMQ-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274408#comment-13274408
]
Jonathan Anstey commented on AMQ-2502:
--------------------------------------
I'm wondering about this one... in 5.6 with the new optional dependency on
activemq-pool, now Maven users the activemq-camel component will fail OOTB. The
default behavior is to use pooling, so it isn't an optional dependency by
default :) The workaround right now is to always depend on activemq-pool when
using activemq-camel.
Maybe we should remove that optional tag from the activemq-pool Maven
dependency? WDYT?
> activemq-camel is missing an optional Import-Package for
> org.apache.activemq.pool
> ---------------------------------------------------------------------------------
>
> Key: AMQ-2502
> URL: https://issues.apache.org/jira/browse/AMQ-2502
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0, 5.3.0
> Reporter: Phil Messenger
> Assignee: Gary Tully
> Fix For: 5.3.1, 5.4.0, 5.6.0
>
>
> If pooling is used, org.apache.activemq.pool.PooledConnectionFactory is
> instantiated using reflection. BND does not detect this, so compliant OSGI
> containers will throw a class not found exception. To fix, the following line
> should be added to the <activemq.osgi.import.pkg /> section of the pom:
> org.apache.activemq.pool;resolution:=optional,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
