If I get you correctly, you are saying that JBoss 3 doesn't deploy applications when the server start up right?
If that is so, then, it didn't happen in my case. My ear app can be deployed successfully when I start up JBoss 3.
You mentioned that the deployment will fail when the resouces are not bounded.
It didn't happen to me either. If you notice the console output, JBoss deploys all the configuration, JNDI stuff, DataSource stuff, JMS stuff before actually opening up the EAR and deploy the EJBs and WARs inside it.
So, I can't imagine the reason behind what you said. Possible for you to elaborate more on this?
I have similar experience with dschalle.
In JBoss 3.0.0, it seems OK.
But after upgraded to JBoss 3.0.1 [3.0.1 Date:200208062340], everytime I start JBoss, I got something like
org.jboss.deployment.DeploymentException: SampleDS not bound
and my connection pool is not functioning. I have to manually deploy firebird-service.xml and then the connection pool is bound OK.
So everytime I start JBoss 3.0.1, I have to manually deploy firebird-service.xml, and this is quite annoying.