Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
It uses the MQSeries API to create the connection factory and queue objects, but those objects get registered in the JNDI namespace of JBoss itself.
Basically, this is something very similar to the jbossmq-destinations.xml but for
reused to figure out how to configure weblogic JMS in
> JBoss (the initial email of this list).
>
> Thomas Cherel
>
> -Original Message-
> From: Adrian Brock [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 29, 2003 7:49 AM
> To: [EMAIL PROTECTED]
> Subject: RE:
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
I know this patch, I submitted it :-)
The patch contains much more details that what we discussed and can probably be reused to figure out how to configure weblogic JMS in JBoss (the initial email of this list).
Thomas Cherel
Thanks for the details.
Thomas Cherel
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 7:53 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
On Fri, 2003-08-29 at 03:06, [EMAIL PROTECTED] wrote:
> Qu
k [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 7:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
>
> This is sore point in the spec :-)
> It leaves it for each JMS implementation to solve. It implements the
> Connect
On Fri, 2003-08-29 at 02:38, [EMAIL PROTECTED] wrote:
> Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 -
> also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended
> Transactional Clients - which requires CSD03) you have the support fro
> XAConnectionFactory and through r
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Quick question related to the remote invoker proxy binding.
Is it something new (this invoker proxy binding) in JBoss 3.2 to avoid creating a complete different container-configuration?
In JBoss 3.0.5, when bringing MQSeries as a JMS
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
Actually, in the latest MQSeries (WebSphere MQ 5.3.0.2 with CSD03 - also called WebSphere MQ 5.3.0.3 - and the WebSphere MQ Extended Transactional Clients - which requires CSD03) you have the support fro XAConnectionFactory and through
at up.
>
> Thanks for your time,
> Dustin
>
> > -Original Message-
> > From: Adrian Brock [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, August 28, 2003 2:55 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
XA database sources).
>
> Thomas Cherel
>
>
>
> -Original Message-
> From: Adrian Brock [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 2:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
>
> N
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
When configuring WebLogic as a JMS provider within JBoss, the MDB will get a WebLogic session. If this is an XA compliant session, then it can be enlisted in the JBoss TM (see JMS spec, where, on a XASession, you can say, getXAResource
ian Brock [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 2:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
>
>
> No, a distributed TM is only required when there are multiple
> transaction managers.
>
> The JB
Title: RE: [JBoss-user] JMS: JBoss to Weblogic messaging
I managed to have MQSeries configured as a JMS provider in JBoss (and then have JBoss MDB listening to MQ queues). But XA support did not work (got an answer from on of the JBoss developer mentioning some incompatibility between what
gt;
> Dustin
>
> > -Original Message-
> > From: Adrian Brock [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, August 28, 2003 1:24 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging
> >
> >
> > T
an Brock [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 1:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JMS: JBoss to Weblogic messaging
>
>
> There are two types of interoperability.
>
> JBoss MDB can use any messaging system (it doesn't care
There are two types of interoperability.
JBoss MDB can use any messaging system (it doesn't care about jbossmq)
Different JMS systems can transport each others messages
(typically by wrapping them in their own native message) -
this is obviously slower than a uniform environment.
Regards,
Adrian
Curley, John wrote:
Hi, All:
Can anyone give me feedback on performing JMS messaging to/from
JBoss/WebLogic environments?
Should there be any issues with guaranteed messaging?
In theory, there should be interoperability between the two environments as
implied by the J2EE specification.
Not rea
17 matches
Mail list logo
