Forums

Home » Liferay Portal » Español » General »

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Mauricio Cubillos
Problema Orbeon-portlet sobre Glassfish
June 3, 2008 8:27 PM
Answer

Mauricio Cubillos

Rank: Regular Member

Posts: 118

Join Date: April 18, 2007

Recent Posts

Hemos estado haciendo pruebas con el portlet de ejemplo de Orbeon (sample-orbeon-forms-portlet.war) en nuestro portal montado sobre Glassfish V2, el portal fué desplegado usando el WAR de Liferay (no el Bunbled) y sobre una base de datos PostgreSQL, el problema es que el portlet parece desplegar, el WAR aparece en la carpeta Autodeploy, pero nunca sale en la lista de portlets y en los logs sale el siguiente error

#|2008-06-03T21:57:14.437-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=14;_ThreadName=Timer-5;Deployment descriptor file WEB-INF/web.xml in archive [sample-orbeon-forms-portlet].;232;11;The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".;_RequestID=01c36b1b-3343-4e30-a2dd-92a4d134f23b;|"DPL8015: Invalid Deployment Descriptors in Deployment descriptor file WEB-INF/web.xml in archive [sample-orbeon-forms-portlet].
Line 232 Column 11 -- The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)"."|#]

[#|2008-06-03T21:57:14.437-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=14;_ThreadName=Timer-5;The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".;_RequestID=01c36b1b-3343-4e30-a2dd-92a4d134f23b;|"DPL8005: Deployment Descriptor parsing failure : The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)"."|#]

[#|2008-06-03T21:57:23.234-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=14;_ThreadName=Timer-5;_RequestID=01c36b1b-3343-4e30-a2dd-92a4d134f23b;|Exception occured in J2EEC Phaseorg.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [sample-orbeon-forms-portlet] Line 232 Column 11 -- Deployment descriptor file WEB-INF/web.xml in archive [sample-orbeon-forms-portlet].  The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:380)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.loadDescriptors(ModuleDeployer.java:423)
    at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeployer.java:157)
    at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:179)
    at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:564)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:545)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:492)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:267)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
Caused by: org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".
    at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:304)
    at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:226)
    at com.sun.enterprise.deployment.archivist.Archivist.readStandardDeploymentDescriptor(Archivist.java:480)
    at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:305)
    at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:213)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:763)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
    ... 32 more
|#]

Lo mas extraño es que aun con el Bundled de Glassfish recién bajado de la página de Liferay tampoco funciona pero con el Bundled de Jboss+Tomcat si, funciona, aunque el error pareciera no tener nada que ver.

Alguien le ha pasado lo mismo? alguien ha tratado con está misma configuración de desplegar el Portlet de ejemplo de Orbeon?
Raju Uppalapati
RE: Problema Orbeon-portlet sobre Glassfish
June 3, 2008 10:44 PM
Answer

Raju Uppalapati

Rank: Junior Member

Posts: 66

Join Date: October 24, 2007

Recent Posts

El error indica que el web.xml generado / modificado por el despliegue de portlets Liferay clases no está siguiendo la especificación servlet DTD. ¿Puede usted dar una URL donde los portlets GUERRA archivo puede ser descargado?
¿Qué versión de Liferay está usando?
La cuestión es reproducible con el Liferay-Glassfish paquete?

_raju
Mauricio Cubillos
RE: Problema Orbeon-portlet sobre Glassfish
June 4, 2008 9:51 AM
Answer

Mauricio Cubillos

Rank: Regular Member

Posts: 118

Join Date: April 18, 2007

Recent Posts

La versión de Liferay es 5.0.1RC pero el problema no9 es la versión, ni la incompatibilidad con el DTD, ya que con la misma versión (pero en distinto servidor EJ: JBoss) y el mismo Portlet funciona bien, el problema parece ser solo con Glassfish, sea uasando el Bundeld o desplegando el WAR por aparte.

Raju, If you want, reply me in English.
Raju Uppalapati
RE: Problema Orbeon-portlet sobre Glassfish
June 4, 2008 10:22 AM
Answer

Raju Uppalapati

Rank: Junior Member

Posts: 66

Join Date: October 24, 2007

Recent Posts

Being able to communicate in English makes it much easier. I was typing my message in English and using Google Tanslator :-)

I think I know the root cause:
There seems to be a bug in the Portlet Deployer of Liferay 5.0.1. It is introducing an additional garbage chars when parsing and updating the web.xml of the this plugin portlet WAR file.

<web-app>&gt;
<display-name>sample-orbeon-forms-portlet</display-name>

jar -xvf liferay-portal-5.0.1/glassfish/domains/domain1/autodeploy/sample-orbeon-forms-portlet.war WEB-INF/web.xml
to see the corrupt web.xml
edit the web.xml to remove the &gt; and
jar -xvf liferay-portal-5.0.1/glassfish/domains/domain1/autodeploy/sample-orbeon-forms-portlet.war WEB-INF/web.xml

This will redeploy the war file and it deploys fine now.


_raju
Raju Uppalapati
RE: Problema Orbeon-portlet sobre Glassfish
June 4, 2008 2:30 PM
Answer

Raju Uppalapati

Rank: Junior Member

Posts: 66

Join Date: October 24, 2007

Recent Posts

Ok another update on this issue. Its not reproducible on the Liferay trunk.
A small correction in the workaround in my previous response:

After editing the web.xml to remove the corrupted chars.
You have to use the jar -uvf to update the WAR file ... i typed it incorrectly as jar -xvf in my previous email

_raju
Mauricio Cubillos
RE: Problema Orbeon-portlet sobre Glassfish
June 4, 2008 2:47 PM
Answer

Mauricio Cubillos

Rank: Regular Member

Posts: 118

Join Date: April 18, 2007

Recent Posts

Thank you very much Raju, finally Works perfectly, your post was very useful for us, now another question, this is a bug for all portlets, or is only with the Orbeon Portlet?

one more time, Thank you and sorry about my English emoticon
Raju Uppalapati
RE: Problema Orbeon-portlet sobre Glassfish
June 4, 2008 4:25 PM
Answer

Raju Uppalapati

Rank: Junior Member

Posts: 66

Join Date: October 24, 2007

Recent Posts

I am not sure about the rest of the samples. Most likely not an issue with the rest of them. Otherwise we would have seen more emails on the Liferay forums. Liferay 5.0.2 bits when available for download will resolve this issue for you.

_raju