Deploying the application as disabled should do what you want: the bits are
where they need to be but none of the containers have started the app. That
means users cannot access web locations (they will get 404s), MDBs will not
be available, etc.
There is currently no way to autodeploy an app in a disabled state. You
will need to use either the asadmin deploy command with --enabled=false or
use the corresponding feature of the admin console. As you mentioned, using
autodeploy will deploy the app in an enabled state.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/867119