On Mon, Jun 10, 2002 at 02:08:16PM -0400, David Jencks wrote:
> On 2002.06.10 13:45:14 -0400 [EMAIL PROTECTED] wrote:
> > It seems like the problem is that it can't find the code, which is
> > deployed in another jar in the deploy-dir. I did't include a depend for
> > this, because it says in the
On 2002.06.10 13:45:14 -0400 [EMAIL PROTECTED] wrote:
> It seems like the problem is that it can't find the code, which is
> deployed in another jar in the deploy-dir. I did't include a depend for
> this, because it says in the doc that it will automatically wait for the
> code to be deployed. Doe
It seems like the problem is that it can't find the code, which is deployed in another
jar in the deploy-dir. I did't include a depend for this, because it says in the doc
that it will automatically wait for the code to be deployed. Does't this work?
Adding
to the *service.xml-file solved
There are several possible things that might be happening, it's hard to
tell which one is most likely.
You probably need to have a depends tag in the mbean that uses jms with the
object name of the mbean for the jms queue. You also need to make sure you
are implementing the jboss mbean lifecycle
I have a mbean deployed with a name-service.xml. The code is in a .jar
file also deployed.
When I start jboss, the service isn't started (I get no errors), but if
I touch it after jboss is fully started, it starts and works normally.
The MBean uses JMS, and connects to a queue described in anot
