log4j.lcf
author Víctor Martínez Romanos <victor.martinez@openbravo.com>
Thu, 25 Jun 2015 18:56:49 +0200
changeset 27157 d7e8168bd47b
parent 5808 fd6f3ff0d871
permissions -rw-r--r--
Related to issue 30057: code review preview

Removed flushes from RoleEventHandler because they create conflicts. As a consequence we lose the ability to clear the session, but this shouldn't be a problem because it's very unlikely to have environments with great amount of organizations.
In RoleEventHandler we only create access to * organization when access level is Client (before this changeset it created also records for other organizations and it is useless).
Reverted changes for Initial Client/Organization Setup. RoleEventHandler won't do anything if executed from an Initial Client/Organization Setup (this change is a way to isolate the problems reported at #30253)
Added log4j to RoleEventHandler.
Removed admin mode from RoleEventHandler because it's not needed (the user always has access t the entities involved in the process).
# Set root category priority to DEBUG and its only appender to A1.
log4j.rootCategory=WARN, A1
  
# A1 is set to be a ConsoleAppender. 
log4j.appender.A1=org.apache.log4j.ConsoleAppender
  
# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c - %m%n

log4j.category.org.openbravo.wad=DEBUG