Interesting idea. The only question I have is how do we allow for
messages that contain stack traces using this file format?
-dain
On Apr 5, 2006, at 11:37 AM, Sachin Patel wrote:
Could we just provide a single status file for all archives with
info like... This way rather then a user having to traverse
directories all the info is available in the single file.
ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
- sachin
On Apr 5, 2006, at 2:31 PM, Aaron Mulder wrote:
That's a cool idea, but we have to make sure to delete the entry in
the stopped dir if you deploy successfully later. And we still have
to delete the entry in whatever place if you subsequently un/re/
deploy
through the deploy tool or console, etc.
Aaron
On 4/5/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
I been thinking that we could have sub-directories under deploy that
we move the deployment to when it is stopped or has a deployment
failure. We could also write a note to the faild dir with a reason
for it being in that dir. I'm thinking of something like this:
Starting/Running:
deploy/foo.war
Stopped:
deploy/stopped/foo.war
Failed:
deploy/stopped/foo.war
deploy/stopped/foo.war.txt
What do you think?
-dain
On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
Sure, you can create a JIRA and post a patch.
Thanks,
Aaron
On 4/5/06, Mansoor <[EMAIL PROTECTED]> wrote:
Thanks Aaron for your prompt response ,
I was thinking , whether we can put this feature into our
geronimo.
Infact i have written a piece of code , that removes this
problem.should i
need to raise a jira and submit as a patch ?
On 4/5/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
OK. For now, we recommend that you only use one deployment
method on
any given application -- always use the hot deploy dir, or always
use
the command-line deploy tool, etc. It's definitely possible to
confuse things at the moment by switching techniques for the same
application or module.
Thanks,
Aaron
On 4/5/06, lak n < [EMAIL PROTECTED]> wrote:
Hot deployment Issue :
When already an application module say (hello.war) is
deployed
(either
by using manually or hot deploy procedure ) , And when some one
try to
hot
deploy the same application with same or different name ( say
hello.war
|
hello2.war | hello2 directory ) , the server throws an
exception saying
there exists already an application deployed , But doesn't
delete the
module
( hello.war | hello2.war | hello2 directory) from hot deploy
directory
thus the next time the server starts , it tries to deploy the
same
module
once again.
I think the better option in this case would be to delete the
unsuccessfully hot deployed application file or directory
from hot
deploy
directory and show some message.
With Thanks and Regards,
Mansoor
