I've lost track of where this destination is being created. Is it
automatic from the jndi lookup?
david jencks
On 2002.05.01 15:00:52 -0400 Adrian Brock wrote:
Well done David.
The JBossMQ problem is because it creates a Destination
MBean directly in the ServiceController without
Yes,
It creates the Queue if it doesn't exist.
Look in org.jboss.ejb.plugins.jms.JMSContainerInvoker
at createDestination(...)
Regards,
Adrian
I've lost track of where this destination is being
created. Is it
automatic from the jndi lookup?
david jencks
On 2002.05.01 15:00:52 -0400
:[EMAIL PROTECTED]]On Behalf Of Hiram
Chirino
Sent: Thursday, May 02, 2002 2:36 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Running testsuite twice almost works
now.(Branch_3_0)
I feel like ripping that code out of the JMSContainerInvoker! It
ties the
JMSContainerInvoker down tightly
it
more elegently at the org.jboss.jms.jndi.JMSProviderAdapter level.
Does anybody oppose?
Regards,
Hiram
From: Adrian Brock [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Running testsuite twice almost works
now.(Branch_3_0)
Date: Thu, 2 May
at the org.jboss.jms.jndi.JMSProviderAdapter level.
Does anybody oppose?
Regards,
Hiram
From: Adrian Brock [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Running testsuite twice almost works
now.(Branch_3_0)
Date: Thu, 2 May 2002 12:06:20 -0500
Yes
With the changes I checked in this morning last night I got only 3 errors
running the testsuite 6 times for Branch_3_0
2 of these are from jrmp CustomSockets tests, so I think they might have
the same problem the security tests with custom sockets had.
The remaining failure is jsr-77
Well done David.
The JBossMQ problem is because it creates a Destination
MBean directly in the ServiceController without
specifying any dependencies. It gets destroyed
with the ServiceController, after the service it
requires has gone.
Anybody know what the dependency should be?
