[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=12998969#comment-12998969 ] 

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

[16:47] <chirino> yeah.. so I'd just use new ActiveMQConnectionFactory(url)
[16:47] <chirino> and make url configurable.
[16:47] <chirino> when in fabric, configure url="fabric://default"
[16:48] <chirino> and the client will connect to a random broker in the default group.
[16:48] <chirino> if not in fabric, configure url to be something like: "failover://(tcp://localhost:61616)"
[16:48] <chirino> where your explictly configuring where the broker is running. 
[16:50] <virchete> by default that is the port
[16:50] <virchete> 61616
[16:50] <chirino> yeah
[16:50] <virchete> ok man
[16:50] <virchete> very helpful
[16:51] <virchete> if anytime you have a doubt about jboss overlord project
[16:51] <virchete> come to me
[16:51] <virchete> xD
[16:51] <chirino> ok thx!

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