geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tina Li (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6028) CounterApp_1.0.0.eba can not be hotdeployed and nothing changed when rehotdeploy another eba application
Date Wed, 29 Jun 2011 09:39:28 GMT


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.schema.SchemaTypeLoaderBase.parse(
	at org.apache.xmlbeans.XmlObject$Factory.parse(
	at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.parse(
	at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.identifySpecDDSchemaVersion(
	at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.basicInitContext(
	at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.initContext(
	at org.apache.geronimo.osgi.web.extender.WebApplication.doRun(
	at java.util.concurrent.Executors$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$
Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA
	at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(
	at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(
	... 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:
>             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:


View raw message