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 
  <classpath codebase="deploy"
             archives="smsapp.jar"/>

to the *service.xml-file solved the problem, but should it be needed? If no, there 
probably is a bug.
I guess adding the jar to a .sar would give the same result?


Log output:

2002-06-10 19:37:44,605 INFO� [org.jboss.deployment.MainDeployer] Starting deployment 
of package: file:/home/marius/tmp/jboss-3.0.0/server/default/deploy/sms-service.xml
2002-06-10 19:37:44,605 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment 
(init step) of package at: 
file:/home/marius/tmp/jboss-3.0.0/server/default/deploy/sms-service.xml
2002-06-10 19:37:44,606 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL 
with url 
file:/home/marius/tmp/jboss-3.0.0/server/default/tmp/deploy/server/default/deploy/sms-service.xml/69.sms-service.xml
2002-06-10 19:37:44,606 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository] 
UnifiedLoaderRepository adding org.jboss.mx.loading.UnifiedClassLoader@5dc05f7a{ 
url=file:/home/marius/tmp/jboss-3.0.0/server/default/tmp/deploy/server/default/deploy/sms-service.xml/69.sms-service.xml
 }
2002-06-10 19:37:44,606 DEBUG [org.jboss.system.ServiceCreator] About to create bean: 
user:service=SMS2002-06-10 19:37:44,606 DEBUG [org.jboss.system.ServiceCreator] code: 
no.polardesign.boostcom.sms.JBossSMSService
2002-06-10 19:37:44,607 DEBUG [org.jboss.system.ServiceCreator] Class not found for 
mbean: user:service=SMS



On Sun, 2002-06-09 at 13:52, David Jencks wrote:
> 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 and waiting until the start step
> to try to access anything set up be mbeans you depend on.
> 
> Currently there is no way to wait or depend on a jndi entry, you have to
> find an mbean that sets up the jndi entry and depend on it.
> 
> david jencks
> 
> On 2002.06.08 07:29:18 -0400 Marius Kotsbak wrote:
> > 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 another
> > *-service.xml. Do I have to specify dependency on JMS, naming, or the
> > queues (I didn't see any deps in the JNDIMap-example, which use jndi)?
> > If so, how what MBeans do I specify?
> > 
> > Marius
> > Boostcom 
> > 
> > 
> > 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas - 
>http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to