留言板

Deployment of Portlets not possible

Stefan Zülch,修改在14 年前。

Deployment of Portlets not possible

New Member 帖子: 4 加入日期: 10-2-3 最近的帖子
Hi.
We are experiencing a strange problem when trying to deploy our newly developed portlets. We are using Liferay 5.2.3 and the portlets are based on the Liferay SDK. Everything worked fine till a few days ago the deployment on Tomcat (6.0.18) wasn't possible anymore.
Everytime we try to start a deployment we receive the following error message:

10:13:21,404 ERROR [PortletLocalServiceImpl:542] com.liferay.portal.kernel.xml.DocumentException: http://www.liferay.com/dtd/liferay-portlet-app_5_3_0.dtd Nested exception: http://www.liferay.com/dtd/liferay-portlet-app_5_3_0.dtd
com.liferay.portal.kernel.xml.DocumentException: http://www.liferay.com/dtd/liferay-portlet-app_5_3_0.dtd Nested exception: http://www.liferay.com/dtd/liferay-portlet-app_5_3_0.dtd
	at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:377)
	at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:388)
	at com.liferay.portal.kernel.xml.SAXReaderUtil.read(SAXReaderUtil.java:156)
	at com.liferay.portal.service.impl.PortletLocalServiceImpl._readLiferayPortletXML(PortletLocalServiceImpl.java:904)
	at com.liferay.portal.service.impl.PortletLocalServiceImpl.initWAR(PortletLocalServiceImpl.java:486)
	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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
	at $Proxy49.initWAR(Unknown Source)
	at com.liferay.portal.service.PortletLocalServiceUtil.initWAR(PortletLocalServiceUtil.java:184)
	at com.liferay.portal.deploy.hot.PortletHotDeployListener.doInvokeDeploy(PortletHotDeployListener.java:230)
	at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:127)
	at com.liferay.portal.kernel.deploy.hot.HotDeployUtil._doFireDeployEvent(HotDeployUtil.java:108)
	at com.liferay.portal.kernel.deploy.hot.HotDeployUtil._fireDeployEvent(HotDeployUtil.java:153)
	at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:43)
	at com.liferay.portal.kernel.servlet.PortletContextListener.portalInit(PortletContextListener.java:113)
	at com.liferay.portal.kernel.util.PortalInitableUtil.init(PortalInitableUtil.java:48)
	at com.liferay.portal.kernel.servlet.PortletContextListener.contextInitialized(PortletContextListener.java:109)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:926)
	at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:889)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
	at org.apache.catalina.core.StandardService.start(StandardService.java:516)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
	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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)


It seems that Liferay is validating the xml files against a dtd (liferay-portlet-app_5_3_0.dtd) that we are not using and hence won't deploy the portlets. Is anyone experiencing the same problem and has an idea on how to solve it?
Otherwise we are in big trouble cause development isn't possible anymore.
thumbnail
Mika Koivisto,修改在14 年前。

RE: Deployment of Portlets not possible

Liferay Legend 帖子: 1519 加入日期: 06-8-7 最近的帖子
Check your liferay-portlet.xml that it isn't referring to 5.3.0 dtd. It should refer to 5.2.0 instead.
Stefan Zülch,修改在14 年前。

RE: Deployment of Portlets not possible

New Member 帖子: 4 加入日期: 10-2-3 最近的帖子
Hi Mika, thanks for the quick reply. I'v checked liferay-portlet.xml and it is refering to 5.2.0. That's what's so strange about the error message. As I said, the problem appeared somehow out of nowhere a few days ago. I cannot imagine that ther aren't any other developers out there that are experiencing the same problems.