search

PILLUTLAAVINASH / google-enterprise-connector-manager

Automatically exported from code.google.com/p/google-enterprise-connector-manager
0 stars 0 forks source link

Move Feed Logging properties to logging.properties #163

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently logging configuration is specified in:
  logging.properties
  applicationContext.xml
  applicationContext.properties

The feed logging FileHandler filename pattern and the feed logging level should 
be moved to 
logging.properties (from applicationContext.xml and 
applicationContext.properties, 
respectively).

If we committed to using the JULI log manager, we wouldn't need any 
configuration of 
FeedLogging in applicationContext.xml, as JULI supports multiple named 
FileHandlers.  If we 
don't commit to using JULI, we must still set up the feed logging FileHandler, 
via Spring.  
However it could still get its logging level and filename from 
logging.properties.

We should also consider moving the teedFeedFile configuration to 
logging.properties, but that 
is less obvious.

This would consolidate all user/admin-configurable logging properties in a 
single place.  This 
makes it easier for the administrator and google support.  It would also make 
implementing 
Issue 104 (servlet to change logging levels) much easier.

See also Issue 104
See also Issue 154

Original issue reported on code.google.com by Brett.Mi...@gmail.com on 19 Jun 2009 at 10:00

GoogleCodeExporter commented 8 years ago

Original comment by Brett.Mi...@gmail.com on 30 Jun 2009 at 12:13

GoogleCodeExporter commented 8 years ago

Original comment by jl1615@gmail.com on 25 Sep 2009 at 1:29

GoogleCodeExporter commented 8 years ago 
From Marty, 25 Sep 2009:

/changes/Brett.Michael.Johnson/issue_106/trunk/projects/connector-manager/etc/ap
plicationContext.xml   
r2251   line 74:
74:   <bean id="FeedWrapperLogger"
I know we have talked about making this logger consistent with other loggers, 
however, would it be better (or 
worth it at this point) to move this logger out of DocPusher and into the 
DocPusherFactory.  Doesn't feel right 
to be working on the DocPusher class when it's not actually managed as a bean.

Original comment by Brett.Mi...@gmail.com on 6 Oct 2009 at 9:01

GoogleCodeExporter commented 8 years ago

Original comment by mar...@google.com on 4 Dec 2009 at 11:04

GoogleCodeExporter commented 8 years ago 
This issue is filed as Google issue #6514070

Original comment by tdnguyen@google.com on 18 May 2012 at 9:27