geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tina Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy a re-named eba application
Date Wed, 24 Aug 2011 10:11:29 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090126#comment-13090126
] 

Tina Li commented on GERONIMO-6028:
-----------------------------------

Hi Rex, 
I found a problem like this:
1.Hotdeploy eba application:blueprint-eba-3.0-SNAPSHOT.eba successfully
2.Rename blueprint-eba-3.0-SNAPSHOT.eba to blueprint-eba1-3.0-SNAPSHOT.eba 
3.Hotdeploy blueprint-eba1-3.0-SNAPSHOT.eba without uninstall blueprint-eba-3.0-SNAPSHOT.eba
and there's a warning message prompted.
4.Delete blueprint-eba-3.0-SNAPSHOT.eba first, then this eba application was deleted
5.Restart the geronimo server and still can't find the deleted blueprint eba application althouth
the file "blueprint-eba1-3.0-SNAPSHOT.eba" still exited under the folder <geronimo_home>/deploy/
6.Hot deploy this eba application again named "blueprint-eba1-3.0-SNAPSHOT.eba" which will
override the existed file that named "blueprint-eba1-3.0-SNAPSHOT.eba" (refer to step3)
7.Then you can find this eba application was not deployed.
Please have a check. 
Thank you!

> Nothing prompted when hotdeploy a re-named eba application
> ----------------------------------------------------------
>
>                 Key: GERONIMO-6028
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6028
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, osgi
>    Affects Versions: 3.0
>         Environment: OS:win2008r2x64
> JDK:IBM jdk Java60 SR9 FP1
>            Reporter: Tina Li
>            Assignee: Rex Wang
>             Fix For: 3.0
>
>         Attachments: geronimo.log
>
>
> 1.Hotdeploy eba application:blueprint-eba-3.0-SNAPSHOT.eba successfully
> 2.Rename blueprint-eba-3.0-SNAPSHOT.eba to blueprint-eba1-3.0-SNAPSHOT.eba 
> 3.Hotdeploy blueprint-eba1-3.0-SNAPSHOT.eba without uninstall blueprint-eba-3.0-SNAPSHOT.eba
> 4.Found nothing changed.But according to GERONIMO-5832 of Rex's comments:
> "hot deploy a XXX.eba and then put in a XXX2.eba, (the XXX2.bea is made by rename the
XXX.bea) This scenario supposes to redeploy the eba with the same config id, and after the
XXX2.eba's deployment, the XXX.eba should be deleted."

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message