You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org> on 2005/06/20 20:25:19 UTC
[jira] Updated: (BEEHIVE-626) web service control has debug log4j logging enabled
[ http://issues.apache.org/jira/browse/BEEHIVE-626?page=all ]
Eddie O'Neil updated BEEHIVE-626:
---------------------------------
Fix Version: v1m1
Environment:
This was fixed in v1m1 setting fix version correctly.
> web service control has debug log4j logging enabled
> ---------------------------------------------------
>
> Key: BEEHIVE-626
> URL: http://issues.apache.org/jira/browse/BEEHIVE-626
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: v1m1
> Reporter: Jim Cummings
> Fix For: v1m1
>
> The web service control being migrated over from control haus has debug logging enabled in its log4j.properties file. This can cause clients who do not explicitly set -Dlog4j.configuration to their own properties file to suddenly see lots of debug logging for anything that uses log4j under-the-covers if the web service control is in their classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira