You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Tina Li (JIRA)" <ji...@apache.org> on 2011/06/29 11:17:53 UTC
[jira] [Created] (GERONIMO-6028) CounterApp_1.0.0.eba can not be
hotdeployed and nothing changed when rehotdeploy another eba application
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
Priority: Minor
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
[jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy
a re-named eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066763#comment-13066763 ]
Rex Wang commented on GERONIMO-6028:
------------------------------------
I updated the description.
Now, if we meet such situation, there will be a warning message prompted.
commit at revision: 1147721 in trunk
-Rex
> 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
[jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy
a re-named eba application
Posted by "Tina Li (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (GERONIMO-6028) CounterApp_1.0.0.eba can not be
hotdeployed and nothing changed when rehotdeploy another eba application
Posted by "Tina Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057128#comment-13057128 ]
Tina Li commented on GERONIMO-6028:
-----------------------------------
Follow the above steps 1~8 then
Restart the server and found error message:
2011-06-29 17:35:51,008 ERROR [AbstractWebModuleBuilder] Fail to identify web.xml schema version
org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486)
at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:712)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:696)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:683)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208)
at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:633)
at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.parse(XmlBeansUtil.java:102)
at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.identifySpecDDSchemaVersion(AbstractWebModuleBuilder.java:519)
at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext(AbstractWebModuleBuilder.java:486)
at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.initContext(AbstractWebModuleBuilder.java:434)
at org.apache.geronimo.osgi.web.extender.WebApplication.doRun(WebApplication.java:211)
at org.apache.geronimo.osgi.web.extender.WebApplication.run(WebApplication.java:124)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:736)
Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454)
... 17 more
2011-06-29 17:35:51,149 INFO [ModuleHandler] Deployed application/CounterApp/1.0.0/eba
> 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
> 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
[jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy
a re-named eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066765#comment-13066765 ]
Rex Wang commented on GERONIMO-6028:
------------------------------------
found another issue: we should not calculate the configId from a deleted file
commit the fix At revision: 1147723
-Rex
> 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
[jira] [Updated] (GERONIMO-6028) CounterApp_1.0.0.eba can not be
hotdeployed and nothing changed when rehotdeploy another eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rex Wang updated GERONIMO-6028:
-------------------------------
Description:
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."
was:
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.
Priority: Major (was: Minor)
Fix Version/s: 3.0
> 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
> 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
[jira] [Resolved] (GERONIMO-6028) Nothing prompted when hotdeploy a
re-named eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (GERONIMO-6028) Nothing prompted when hotdeploy a
re-named eba application
Posted by "Tina Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tina Li closed GERONIMO-6028.
-----------------------------
Verified on Aug 23's build.
> 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
[jira] [Updated] (GERONIMO-6028) Nothing prompted when hotdeploy a
re-named eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rex Wang updated GERONIMO-6028:
-------------------------------
Summary: Nothing prompted when hotdeploy a re-named eba application (was: CounterApp_1.0.0.eba can not be hotdeployed and nothing changed when rehotdeploy another eba application)
> 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
[jira] [Commented] (GERONIMO-6028) Nothing prompted when hotdeploy
a re-named eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090229#comment-13090229 ]
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: 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
[jira] [Updated] (GERONIMO-6028) CounterApp_1.0.0.eba can not be
hotdeployed and nothing changed when rehotdeploy another eba application
Posted by "Tina Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tina Li updated GERONIMO-6028:
------------------------------
Attachment: geronimo.log
> 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
> 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
[jira] [Assigned] (GERONIMO-6028) CounterApp_1.0.0.eba can not be
hotdeployed and nothing changed when rehotdeploy another eba application
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ 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