This sounds like its treating the deploy directory as an archive url vs a directory url. This same behavior is seen when not including a trailing '/' on the URLDeploymentScanner so perhaps its a similar configuration issue.
No it is deliberate.
Currently it passes the URL directly to the MainDeployer.
I'd suggest it adds/removes it from the URLDeploymentScanner?
I'm running 4.0.4GA retrofitted with ejb3 RC8 and Seam 1.0.1x
I just created an example hasingleton, i have an example.sar file that seems to be ignored if I drop it into the deploy-hasingleton dir, but seems to function if I drag it into the deploy dir.
In the deploy dir it constructs, and the startSingleton method is called. I see it on the jmx-console, and start/stop work from there - but I'm not convinced I actually had an hasingleton... Did I? Haven't tested in the cluster yet.
I think I need one in order to fire a message into the cluster periodically. The hasingleton w/perhaps quartz seemed like a good idea to solve this problem. Am I on the right track?
How do you deploy an hasingleton?
How do you KNOW its working?
Was the deploy-hasingleton dir ignored?
Does the farm exist? who turned it off? why?
Or perhaps, the question is really - which chapter did I miss?
The deploy-hasingleton directory is not scanned for hot deployment.
You could try this also for a simple hasingleton