MBean nead jars witch nead the DefaultDS, before loaded

[f_kasper]

Hi
I have at problem deploying my MBean (osworkflow interface) to the deploy folder. I get an error telling that it is missing the DefaultDS. But when i deploy it on runtime, there isn't a problem.
So my question is:
Are there any way to delay my own deployment until the default server is deployed (also the classpath files)?
Are the a way to set dependencies to the classpath jars?

I deploy with: osworkflow.sar/META-INF/jboss-service.xml
containing:
<server>
<depends>jboss:service=Naming</depends>
<!--<local-directory path="osworkflow"/> for at skrive til db dir-->
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-beanutils-1.4-dev.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-collections.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/crimson.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/dom4j-1.4-dev-7.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/ejb.jar"/>

<!-- kraever foelgende : -->
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/osuser.jar"/>

<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-dbcp.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-logging.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-jelly-1.0-beta-3.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/commons-pool.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/bsf.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/bsh-1.2b5.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/oscore-2.0.1.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/propertyset-1.0.2_min.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/winger.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/osworkflow-2.1.0_min.jar"/>
<classpath codebase="." archives="winger.sar/test.war/WEB-INF/lib/quartz.jar"/>

<mbean code="org.winger.osworkflow.osWorkflow" name="user:service=osWorkflow">
<!--<depends>jboss.system:type=Log4jService</depends>-->
<attribute name="JndiName">osWorkflow</attribute>
<depends>jboss:service=Naming</depends>
<depends>jboss.jca:service=LocalTxDS,name=hsqldbDS</depends>
</mbean>
</server>

[adrian.brock]

Did you read this post less than 12 hours before?

http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=forums/ you are doing with the classpaths looks horrible :-(

Regards,
Adrian

[f_kasper]

Thanks,
but can you also tell my how to register my jars in the start()?
I have tried looking around in the JBoss dok i have bought without any look and in the source-code for some example. I had an idea about getting the standard deployer and then deploy my jars. But is it the right way to get access to the classes in my jars? or is there some way to just register my jars (import) so my MBean can have access to the required classes?

/kasper

[adrian.brock]

Either put the jars in
server/default/lib
or create a sar

Regards,
Adrian