Anything in the configuration I can do to avoid the warnings? Other than
using log levels?
David Sean Taylor wrote:
On Mon, Mar 22, 2010 at 5:18 AM, David Dyer <[email protected]> wrote:
Since we've begun our upgrade of the tomcat container we're running Jetspeed
under I've been seeing the following WARN message in the console:
WARN org.apache.jetspeed.engine.JetspeedEngine - No ContainerService
defined for org.apache.pluto.services.property.PropertyManagerService
It appears to be non fatal and does nothing but clutter the logs.
A google search brought up this thread from 2008:
http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/200811.mbox/%3c7058448bc5b00647b05e15538ae8bd5801441...@msgmmkcle2win.dmn1.fmr.com%3e
but it doesn't seem to provide any answers.
Any ideas what's causing the warning?
Its an optional service from Pluto 1.0.1 that we don't use in Jetspeed
2.1.x. So it goes to retrieve it, returns null, and its logged as a
warning that the service doesn't exist. The property manager service
is used in Pluto, but its always protected with checks like:
public static Map getRequestProperties(PortletWindow window,
HttpServletRequest request)
{
if (getService() == null)
{
return null;
}
return getService().getRequestProperties( window, request);
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.437 / Virus Database: 271.1.1/2763 - Release Date: 03/22/10 07:33:00
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
