Exception while deploying Message Driven Bean

[mandarm]

Hi,
I see the following exception on console if I put my jar and re-start JBoss.
If I remove my jar and put it after the server has started, it deploys correctly.

Looks like my jar is getting deployed before the DefaultJMSProvider.

---------------------------------------------------
15:37:08,599 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:

Incompletely deployed packages:

MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.j2ee:jndiName=local/StoreAndForwardMessageBean,service=EJB
state: FAILED
I Depend On:
Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound]
15:37:08,614 INFO [URLDeploymentScanner] Started
15:37:08,630 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.1/server/default/conf/jboss-service.xml
15:37:08,646 INFO [Server] JBoss (MX MicroKernel) [3.2.1 (build: CVSTag=JBoss_3_2_1 date=200305041533)] Started in 19s:
94ms
------------------------------

How can I make sure that the order of deployment on server startup is such that this works fine ?
Is there any way in my ejb-jar.xml or jboss.xml file to denote this dependency ?

Thanks
Mandar

[mandarm]

Setting "RecursiveSearch" = true solves my probem.

Now when I start the server, the deploy/jms directory files get deployed before my jar and everything looks fine.

I am not sure if if this is the right way to solve the problem I have.

Thanks
Mandar