I said the same thing, but my message never made it. :/
I think you'd want to leave the file there, because then you can
examine it to see what exactly you deployed... You could also take
that exact artifact and give to someone else for deployment elsewhere
(in QA, for example) confident that what you tested is what you gave
out.
geir
On Oct 24, 2005, at 10:16 AM, Sachin Patel wrote:
Jeff Genender wrote:
Sachin Patel wrote:
Jacek Laskowski wrote:
Am I right that the simplest solution is to develop a GBean that
would monitor a directory and hand over a deployable to a deployer?
This was my thinking as well. The directory would listen for
adds, modifications, and deletions.
I think this may be somewhat confusing. I think when dropping in
the directory, it should should deploy...then be immediately
removed from the directory. IMHO, this dir should be for hot
deploy only. Let the deployer decide if it should be updated or
added. I think the deletions should not be done through this
dir. We should use the normal undeploy capabilities of the deployer.
Wouldn't it be more confusing to the user if their file got removed
after it got deployed? I feel the point of a "live" directory is
for the runtime to be able to react to any changes to it, including
deletions. Both Jboss and Websphere's hot deploy capability allow
deletions.
What does tomcat allow?
Sachin
Jacek
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
