[
https://issues.apache.org/jira/browse/SM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
filippo balicchia updated SM-2183:
----------------------------------
Attachment: SM-2183.patch.txt
Please see the patch:
it includes a little module for register javax.jms.ConnectionFactory in service
registry.
{code:xml}
<cm:property-placeholder
persistent-id="org.apache.activemq.server-default" update-strategy="reload">
<cm:default-properties>
<cm:property name="broker-name" value="amq-broker"/>
</cm:default-properties>
</cm:property-placeholder>
<bean id="activemqConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL"
value="vm://${broker-name}?create=false&waitForStart=10000" />
</bean>
<bean id="pooledConnectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="maxConnections" value="8" />
<property name="connectionFactory" ref="activemqConnectionFactory" />
</bean>
<reference id="recoverableTxManager"
interface="org.apache.geronimo.transaction.manager.RecoverableTransactionManager"
availability="mandatory" />
<!--
Register the javax.jms.ConnectionFactory in the OSGi Service Registry
-->
<service ref="pooledConnectionFactory"
interface="javax.jms.ConnectionFactory">
<service-properties>
<entry key="name" value="localhost"/>
</service-properties>
</service>
</blueprint>
{code}
the patch
-upgrade to activemq-5.9.0
-upgrade to camel-2.13-SNAPSHOT
and feature cfg for apache-servicemix and apache-servicemix-full distribution.
I don't know if persistent-id is the best choice but can be change
Any feedBack are wellcome
> Provide JMS ConnectionFactory in the OSGi Service Registry
> ----------------------------------------------------------
>
> Key: SM-2183
> URL: https://issues.apache.org/jira/browse/SM-2183
> Project: ServiceMix
> Issue Type: Improvement
> Components: assemblies
> Affects Versions: 5.0.0
> Reporter: Gert Vanthienen
> Assignee: Raul Kripalani
> Fix For: 5.0.0
>
> Attachments: SM-2183.patch.txt
>
>
> The new OSGi implementation of ActiveMQ no longer provides a
> {{javax.jms.ConnectionFactory}} service in the OSGi Service Registry.
> We should provide a small glue bundle for
> ActiveMQ (similar to what we do for Activiti) that provides these
> extra services to the container:
> - a plain JMS ConnectionFactory to be used by routes and e.g. by our
> own JMS appender
> - an XA ConnectionFactory that has already been configured to interact
> with the Aries JTA provider we also ship
> Cfr. http://servicemix.396122.n5.nabble.com/smx5-jms-appender-td5716215.html
> for some background on this issue
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
