[
https://issues.apache.org/jira/browse/SM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618316#comment-13618316
]
Gert Vanthienen edited comment on SM-2183 at 3/31/13 12:40 PM:
---------------------------------------------------------------
@Filippo: Thanks for working on this! Personally, I would prefer a solution
that does not replace ActiveMQ's own OSGi bootstrap mechanism, I think.
Perhaps we could look at the JMX MBean and expose those connections for any
broker that gets registered there or read the broker-name value from the
Configuration Admin service or something like that?
I'd consider that a workaround for this release. For a next version, we
probably want to get in touch with the ActiveMQ team to see if
{{activemq-osgi}} can publish some extra information about the brokers it
creates to the OSGi Service Registry so we can react to that instead
was (Author: gertvanthienen):
@Filippo: Thanks for working on this! Personally, I would prefer a
solution that does not replace ActiveMQ's own OSGi bootstrap mechanism, I
think. Perhaps we could look at the JMX MBean and expose those connections for
any broker that gets registered there?
I'd consider that a workaround for this release. For a next version, we
probably want to get in touch with the ActiveMQ team to see if
{{activemq-osgi}} can publish some extra information about the brokers it
creates to the OSGi Service Registry so we can react to that instead
> 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
> Fix For: 5.0.0
>
> Attachments: initialSolution.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
