Exploded WAR are not deployed when context file is copied to the Liferay's hot deploy folder

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 6.0.4 GA
• Component/s: None
• Labels: None
• Environment: Tomcat 5 and 6 / Mac OSX (issue is probably not OS-dependent)
• Similar Issues: Show 5 results ; ;

  LPS-1228	For Exploded Directory Deployment, war directory is not getting massaged properly when portlet.container.implementation=sun
  LPS-1217	Display name of an application is set to wrong value during Exploded Tomcat deployment through context xml file.
  LPS-26262	Exploded deploy a portlet failed
  LPS-31300	Auto deploying Liferay as exploded WAR on JBoss
  LPS-28827	test-pacl-portlet - Distinguish between an exploded and unexploded war file

Deployment of exploded WAR (as indicated at this Wiki page: http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/Fast+Development+of+Liferay+Plugins+with+Tomcat) does not work. When a context file is copied into the hot deploy folder, Tomcat/Liferay reads the file but the app is not recognized as a webapp and therefore not deployed.

To work correctly, the context file has to be copied directly into $TOMCAT_LIFERAY/conf/localhost/Catalina (this task should be normally handled by the Liferay hot deploy process).

Tested with Liferay 5.2 (from trunk version 23509) with Tomcat 6.0.18 and 5.5.27.

[Dale Shan]

It's not a lliferay bug, i will close this ticket.

[Mariusz Nosiński]

Everything goes OK, when you change portal property : 'auto.deploy.tomcat.conf.dir=../conf/Catalina/localhost'
to :
'auto.deploy.tomcat.conf.dir=$

{catalina.base}

/conf/Catalina/localhost'

[Dale Shan]

Thanks for your contribution.

[Jim Breen]

I disagree that this is not a Liferay bug. The bug is that the default value for auto.deploy.tomcat.conf.dir in portal.properties is incorrect. With the default value, any context file dropped in the $LIFERAY_HOME/deploy directory will result in $LIFERAY_HOME/conf/Catalina/localhost/ to be created and the context file copied there instead of to $LIFERAY_HOME/tomcat-x.x.x/conf/Catalina/localhost. This prevents hot deploy of a context file from working unless you override the property in portal-ext.properties.

Mariusz correctly points out that the value for auto.deploy.tomcat.conf.dir should be "$

{catalina.base}

/conf/Catalina/localhost". This value is consistent with the default value in portal.properties for auto.deploy.tomcat.dest.dir.

I've experienced the bug in Liferay 5.2.3

[Michael Saechang]

Closing ticket due to inactivity. If the issue still exist please reopen. Thank you.

[Vicki Tsang]

This is being bulk closed in preparation for the new workflow.