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] [Assigned] (GERONIMO-6028) CounterApp_1.0.0.eba can not be hotdeployed and nothing changed when rehotdeploy another eba application
Date Thu, 30 Jun 2011 02:27:28 GMT

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

Rex Wang reassigned GERONIMO-6028:
----------------------------------

    Assignee: Rex Wang

> CounterApp_1.0.0.eba can not be hotdeployed and  nothing changed when rehotdeploy another
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
>            Priority: Minor
>         Attachments: geronimo.log
>
>
> 1.Use the build:2011.06.21-16:18:09.889+0800-3.0 snapshot of Geronimo server
> 2.Start the server if it's not started
> 3.Hot deploy eba application: CounterApp_1.0.0.eba
>  Copy CounterApp_1.0.0.eba to the <Geronimo_home>/deploy directory without stopping
the server
> 4.Found CounterApp_1.0.0.eba can't be deployed but has no error info.
>  Refer to GERONIMO-5771,this application can be deployed.
> 5.Hotdeploy another eba application:blueprint-eba-3.0-SNAPSHOT.eba successfully
> 6.Rename blueprint-eba-3.0-SNAPSHOT.eba to blueprint-eba-3.0-SNAPSHOT1.eba 
> 7.Hotdeploy blueprint-eba-3.0-SNAPSHOT1.eba without uninstall blueprint-eba-3.0-SNAPSHOT.eba
> 8.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