Hi David,
Just to say thanks for the suggestions. Packaging the ejb jar and
-service.xml into a .EAR worked well.
The one extra thing I had to do was package some support jars into the
EAR as well instead of installing them in deploy/../lib, otherwise I got
class not found errors.
Cheers,
Alex.
-user
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] MBean deployment ignores depends tag
Hi David,
Just to say thanks for the suggestions. Packaging the ejb jar and
-service.xml into a .EAR worked well.
The one extra thing I had to do was package some support jars into the
EAR as well instead
Hi David,
After reading your and Scotts replies I've packaged the mbean classes
and -service.xml into a .sar to try to get the classes loaded.
I have a problem that both my mbean .sar and my ejb .jar both need to
use the EJB interfaces, so I've packaged the interfaces into both the
.sar and the
- Original Message -
From: Alex Hornby [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: jboss-user [EMAIL PROTECTED]; Scott M Stark [EMAIL PROTECTED]
Sent: Monday, June 09, 2003 6:37 AM
Subject: Re: [JBoss-user] MBean deployment ignores depends tag
On Mon, 2003-06-09 at 14
Did anyone have a chance to look at the log files I sent on thursday
last week?
The deployment order seems to be ignoring the dependencies.
Alex.
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger
On Mon, 2003-06-09 at 14:25, Nicholas wrote:
Can you send them again ? I could not find them in the
archive.
Hmmm, looks like the sourceforge archive strips off attachments.
Here is the body of my reply to Scott and the attachment again:
I've attached a gzip'd jboss log from a jboss 3.2.1
I'm seeing a problem deploying an EJB jar and an mbean -service.xml file
into JBoss 3.2.1.
If I copy them into the deployment directory one by one whilst jboss is
running its fine - the EJBs deploy followed by the service MBean.
The problem is that when JBoss is restarted the mbean depends tag
All dendencies must be started before you mbean. Show the
startup message ordering that illustrates otherwise. You say
you specify one ejb dependency. If other ejbs are used
directly or indirectly then some ejbs in the jar may not have
been started when you mbean is started. EJBs are deployed
in
On Thu, 2003-06-05 at 16:45, Scott M Stark wrote:
All dendencies must be started before you mbean. Show the
startup message ordering that illustrates otherwise. You say
you specify one ejb dependency. If other ejbs are used
directly or indirectly then some ejbs in the jar may not have
been
