I'm also looking for this info. It is a real pain to do a jar/war/ear each time.
Yes from 2.4.4 and 3.0RC1
Put your directory in "deploy", make sure they have the
correct extensions .ear, .war, etc.
Did you mean "file" instead of "directory"? How can a directory have the extension of .ear, .war, etc?? You imply a J2EE standard package, not an expanded directory.
Just putting the directory under /deploy doesn't work either - I get the message "<jboss dir>/<my expanded dir> is waiting for an appropriate deployer" from JBoss when it attemps to deploy.
I can do this with 2.4.4 - is it possible with 3.0 RC1 yet? If so, how do I define this?
It is a directory structure that looks like a
The extensions tell jboss how to deploy.
With JBoss 3.0.0 and embedded tomcat 4.0.3 I can't get a .war directory to be deployed even though I put it under the server/default/deploy directory. If I package it up and make it a real .war file it is deployed. However, we would much rather deal with the unpacked version. Is there a configuration option for jboss 3 to turn on or off directory deploying?
Read the previous posting. If u just change the directory name from
ROOT to ROOT.war the app will be using that directory structure.