geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rex Wang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-6028) Nothing prompted when hotdeploy a re-named eba application
Date Mon, 18 Jul 2011 01:52:00 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rex Wang resolved GERONIMO-6028.
--------------------------------

    Resolution: Fixed

> 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