Externalize portal-log4j-ext.xml for easy configuring

• Type: Feature Request
• Status: Contributed Solution
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Portal Services, Portal Services > Configuration Management
• Labels:
  • ee-nf
• Liferay Contributor's Agreement:
  Accept
• Similar Issues: Show 5 results ; ;

  LPS-2879	Easy Configuration For Drop-Down Menus
  LPS-39667	To make configurable the path of the liferay.log file
  LPS-2910	Need an easy UI to configure rules for portlet rendering based on LPS-2909
  LPS-4083	should be able to configure calendar portlet to get/store events from any external Cal-Dav communication suite.
  LPS-26436	Hook Easy Slider cannot deploy use liferay plugin SDK

Currently, there are two ways to configure a portal-log4j-ext.xml file in Liferay.

1. Incorporate it as part of ext-impl.jar
2. Place the file in WEB-INF/classes/META-INF

Neither method lend themselves to easy configuration when using Application Servers that use WAR deployments for Liferay, like WebSphere, WebLogic, or GlassFish, to name a few.

Request: a way to set the location of the liferay logs that is outside any WAR or EAR files, like portal-ext.properties.

[Josef Šustáček]

I've contributed a solution to this, which allows any plugin to specify from where (within it's classloader) should the log4j configuration be read. Then the levels are applied once the plugin is deployed to Liferay – the same way as of the user went to Control Panel and set them.

This way, each plugin could set its own levels (typically, plugins have their own "private" Java packages) or you can have one plugin setting all "portal" levels – instead of EXT.

Josef