Plugging in a module still requires the module to have the correct
capabilities. You can't plug a three prong electrical cord into a
two slot outlet.
----- Original Message -----
From: "Rajkumar Seth" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 27, 2001 6:38 AM
Subject: RE: [JBoss-user] SwiftMQ and JBOSS
> I thought jBOSS was Modular so it is simple to replace jBossMQ with Swift?
>
> -----Original Message-----
> From: Jason Dillon [mailto:[EMAIL PROTECTED]]
> Sent: 2001 June 26 15:23
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] SwiftMQ and JBOSS
>
>
> It is possible to configure JBoss to work with a SwiftMQ provider, but NOT
> for MDB. You can install a SwiftMQJMSProvider, which can return the SwiftMQ
> defined queue/topic/connection references, but since they do not support XA
> or ASF you will have a world of pain trying to get MDB working with it.
>
> You could use the SwiftMQ bridge swiftlet to bridge a SwiftMQ router (or a
> set of routers) to a JBossMQ provider running on each JBoss node (or on just
> one if you like). I ran into some problems doing this when a message
> listener failed to process a message on the target JBossMQ queue. If this
> happened then the message would persist on the local queue, leaving my other
> message consumers (which are attached to other non-local JBossMQ providers)
> unable to attempt to handle those messages.
>
> --jason
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
