I'm experiencing the same issue with a custom theme. My theme so far is very light:
- Created a new theme using the Liferay IDE
- Imported the Classic theme's diff folders (to give me a better starting point for customization)
As others have reported, the error is generated when I first start Eclipse and launch the Liferay server. Restarting the Liferay server (but not Eclipse) resolves the issue. The Update Context Path workaround that Denis suggested unfortunately did not work for me.
One thing I notice in the console log was that upon the first start of the server, I see the following log entries:
Jan 28, 2011 3:02:49 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 57493 ms
15:02:49,571 WARN [ThemeLocalServiceImpl:121] No theme found for specified theme id new_WAR_newtheme. Returning the default theme.
15:02:49,572 WARN [ThemeLocalServiceImpl:121] No theme found for specified theme id new_WAR_newtheme. Returning the default theme.
A few lines later, the logs show all of my plugins being undeployed, then redeployed (I only included the lines concerning the theme plugin below):
Jan 28, 2011 3:02:59 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/new-theme]
Jan 28, 2011 3:02:59 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor new-theme.xml
Jan 28, 2011 3:02:59 PM org.apache.catalina.startup.HostConfig deployDescriptor
WARNING: A docBase C:\liferay-portal-6.0.5\tomcat-6.0.26\webapps\new-theme inside the host appBase has been specified, and will be ignored
15:02:59,849 INFO [ThemeHotDeployListener:78] Registering themes for new-theme
15:03:01,916 INFO [ThemeHotDeployListener:89] 1 theme for new-theme is available for use
At this point, the portal won't work as the theme generates the error. Restarting the server, everything works fine and the last line in the log is "Server startup..."
I have no idea why upon the first startup my plugins are being redeployed, and why it wouldn't do it on the second startup, but it sure seems like this is related to the problem.
Please sign in to flag this as inappropriate.