geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rex Wang (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy a re-named eba application
Date Wed, 24 Aug 2011 13:57:29 GMT


Rex Wang commented on GERONIMO-6028:

you must delete the previous blueprint-eba1-3.0-SNAPSHOT.eba and then put in it again....
otherwise system don't know if you put in a new file.

> Nothing prompted when hotdeploy a re-named eba application
> ----------------------------------------------------------
>                 Key: GERONIMO-6028
>                 URL:
>             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:


View raw message