[overlord-issues] [JBoss JIRA] (SRAMP-561) Support Fuse JMS

[David virgil naranjo (JIRA)]

    [ https://issues.jboss.org/browse/SRAMP-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998948#comment-12998948 ] 

David virgil naranjo commented on SRAMP-561:
--------------------------------------------

This is the IRC conversation with the fuse fabric guys:

<jstrachan> virchete use the JMS API
[16:22] --> theute (~theute at redhat/jboss/theute) se ha unido a este canal.
[16:22] <jstrachan> Queue queue = new ActiveMQ("any.name.you.like")
[16:22] <jstrachan> Queue queue = new ActiveMQQueue("any.name.you.like")
[16:23] <virchete> jstrachan but for example in JBoss EAP you need to define in the standalone-full.xml the queues and topics
[16:23] <chirino> virchete: or session.createQueue("any.name.you.like")
[16:23] <chirino> virchete: jboss likes to make it hard.
[16:23] <chirino> :)
[16:23] <virchete> jaja
[16:23] <virchete> ok chrino
[16:23] <chirino> with activemq things are easy.
[16:23] <virchete> then you mean if
[16:23] <virchete> i include the active mq features
[16:24] <virchete> then using  the Queue queue = new ActiveMQQueue("any.name.you.like")
[16:24] <virchete> would work
[16:24] <chirino> yeah.
[16:24] <chirino> you have code that's using JMS already right?
[16:24] <virchete> yes
[16:24] <chirino> yep
[16:24] <chirino> that's it

> Support Fuse JMS
> ----------------
>
>                 Key: SRAMP-561
>                 URL: https://issues.jboss.org/browse/SRAMP-561
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: David virgil naranjo
>             Fix For: 0.6.0
>
>
> SRAMP-433 created JMS events within S-RAMP.  For Tomcat, Jetty, and standalone EAP,  we use an embedded ActiveMQ broker.  For standalone-full EAP, we re-use the existing HornetQ JMS and JNDI resources.
> Supposedly, Fuse provides ActiveMQ out-of-the-box.  We should re-use that, rather than relying on the embedded broker.  Investigate and figure out a way to add the JMS resources during S-RAMP installation, similar to the new configureJMS-jboss-eap-6.xslt.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)