Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.

[Mansoor]

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