geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <ja...@planet57.com>
Subject Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Date Wed, 05 Apr 2006 19:06:35 GMT
Why not use an XML file for the status?

--jason


On Apr 5, 2006, at 11:52 AM, Dain Sundstrom wrote:

> 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 <dain@iq80.com> 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 <man.geronimo@gmail.com> 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 <ammulder@alumni.princeton.edu> 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 < man.geronimo@gmail.com> 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
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>


Mime
View raw message