log4j.lcf
author Augusto Mauch <augusto.mauch@openbravo.com>
Wed, 05 Jun 2013 14:03:22 +0200
changeset 20511 e426b7ccc826
parent 5839 fd6f3ff0d871
permissions -rw-r--r--
Fixes issue 23996: An event handler has been replaced with database constraints

The event handler TableDataOriginEventHandler has been replaced with database constraints. This is a better approach because it is simpler and easier to maint
ain.

The name of two of the messages has been updated so that it is the name as the constraint that throw them. The message used to warn the user that the table_name must be set if the data origin is 'Table' has been removed because now the table_name is mandatory again in the database.
juanpablo@378
     1
# Set root category priority to DEBUG and its only appender to A1.
juanpablo@378
     2
log4j.rootCategory=WARN, A1
juanpablo@378
     3
  
juanpablo@378
     4
# A1 is set to be a ConsoleAppender. 
juanpablo@378
     5
log4j.appender.A1=org.apache.log4j.ConsoleAppender
juanpablo@378
     6
  
juanpablo@378
     7
# A1 uses PatternLayout.
juanpablo@378
     8
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
juanpablo@378
     9
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c - %m%n
juanpablo@378
    10
asier@683
    11
log4j.category.org.openbravo.wad=DEBUG