Deploying an exploded "war" from a local directory without d

[tomerbd]

Hi

When I specify in jboss-service.xml a directory to be scanned for deployment (sites)

deploy/,file:///c:/Sites/


Then

c:/Sites/SiteA.war is being deployed fine!

However When I specify


deploy/,file:///c:/Sites/SiteA


Then by the log it looks like it was deployed
13:47:30,544 INFO [MainDeployer] Starting deployment of package: file:/c:/Sites/SiteA
13:47:33,178 INFO [MainDeployer] Deployed package: file:/c:/Sites/SiteA

However when I try to access the site in that latter configuration I receive
HTTP Status 404 - /SiteA

Anyone knows why? and how can I deploy that site alone?

(im using jboss3.2.4RC1)
note that I have a jboss-web.xml in SiteA/WEB-INF that specifies my root context to SiteA ...

Thanks in advance...

[darranl]

Because the deployment scanner searched the configured directory for deployable items, by specifying your exploded dir it will scan the contents of it.

[tomerbd]

first i must correct myself I meant:

"deploy/,file:///d:/temp/deploy/"

with the ending slash... yesh its working fine this way, its scanning my deploy directory and deploying all the ear's war's in that directory...

but when I use file:///d:/temp/deploy/app.ear this for an exploded ear it didnt work

so I dont have any problems with scanning, and if it scanned then it shouldnt scanned it ! since the example in jboss-service.xml says :

"
file:/var/opt/myapp.ear
deploy myapp.ear from a local location
"

so why didnt it deploy my exploded app.ear , and if it scanned it it shouldnt have...

[starksm64]

A directory cannot be a deployable, it can only hold deployable content.