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/05/10 05:46:04 UTC

[jira] Resolved: (BEEHIVE-627) Beehive controls should not provide log4j config files

     [ http://issues.apache.org/jira/browse/BEEHIVE-627?page=all ]
     
Eddie O'Neil resolved BEEHIVE-627:
----------------------------------

     Assign To: Zach Smith  (was: Eddie O'Neil)
    Resolution: Fixed

Jim, I think that this was fixed when the system controls came down from ControlHaus.  I've looked through the control JARs and don't see any logging config files. 

Let me know if you have any more trouble with them.

> Beehive controls should not provide log4j config files
> ------------------------------------------------------
>
>          Key: BEEHIVE-627
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-627
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1
>     Reporter: Jim Cummings
>     Assignee: Zach Smith
>      Fix For: V1

>
> Beehive control jars should not provide log4j.* config files in their jars.  This can have unexpected behavior for clients if log4j picks up these unintended config files.
> I believe the webservice control is the only one that does this, but I'm not certain.

-- 
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