Leo Sutic wrote:
From: Peter Donald [mailto:[EMAIL PROTECTED]
+ final String message = "WARNING: " +
m_componentClass.getName() + + " implements the Composable
lifecycle stage. This is " + + " a deprecated feature that
will be removed in the future. " + + " Please upgrade to
using Serviceable.";
+ getLogger().warn( message );
+ System.out.println( message );
Oh god the first explosion was my system log exploding and the second one was the sysadmin shooting me with a sawed-off shotgun.
I'd prefer if this was done at debug level, if at all. And
only on the logger.
If we have to resort to this (even through its a message to the wrong person) it absolutely must not occur more than once in the scope of a JVM sesion. I still favour a seperate audit approach and no logging or System.out.
Cheers, Steve.
With this being printed out on object creation, Cocoon systems will be a firehose with the XML parser being a transient object (non-pooled) IIRC. Given the re-precation being done for Cocoon, which was done because Cocoon still used Composable, I think this will be a horrible user experience.
/LS
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
