You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2013/04/09 11:50:15 UTC

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

    [ https://issues.apache.org/jira/browse/SM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626428#comment-13626428 ] 

Gert Vanthienen commented on SM-2183:
-------------------------------------

The missing ConnectionFactory also causes problems installing some of the examples:

{noformat}
karaf@root> features:install examples-activemq-camel-blueprint 
Error executing command: Can not resolve feature:
Unsatisfied requirement(s):
---------------------------
   service:(service=javax.jms.ConnectionFactory)
      Apache ServiceMix :: Examples :: ActiveMQ Camel Blueprint
{noformat}
                
> 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