[jira] [Updated] (SM-2183) Provide JMS ConnectionFactory in the OSGi Service Registry

["filippo balicchia (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

filippo balicchia updated SM-2183:
----------------------------------

    Attachment: initialSolution.txt

This is a very premature solution for use activemq in servicemix 5 but my goal is to get some feedback about what people aspect from this issue.

At the moment this works for me and the example run well.

The first doubt that comes to me is that in with activemq 5.8.0 I see that was released a new artifact called activemq-osgi and probably people want to reuse that, and the solution that  i proposed is can be replaced with an extensions of that artifact

Anyway,
suggestions, feedback are wellcome for me


Thanks
                
> 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