[ 
https://issues.apache.org/jira/browse/OPENEJB-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

karan singh malhi updated OPENEJB-667:
--------------------------------------

    Attachment: openejb-667.patch

Here is the algorithm for logging:
It is assumed that openejb-core-XXX.jar  has a logging.properties and a 
embedded.logging.properties.
Then we would follow the proposed algorithm:

   - if conf/logging.properties exists, use it
   - if conf/ directory exists, install openejb-core.jar!/logging.properties to 
conf/logging.properties and use it. If logging.properties not found in the jar 
file (not possible ) then use log4.configuration system property and also 
display an error in the console that logging.properties file is missing
        
   - else assume embedded and use openejb-core.jar!/
embedded.logging.properties.If embedded.logging.properties not found in the jar 
file (not possible ) then use log4.configuration system property and also 
display an error in the console that embedded.logging.properties file is 
missing. This has an advantage in tests in that one could simply create their 
own my.embedded.logging.properties file with their own custom logging 
configuration and update the log4.configuration system property to point to 
my.embedded.logging.properties file. This way you can really do custom logging 
without changing anything in embedded.logging.properties (and then reverting it 
back before submitting a patch). 

The logging.properties would be setup with file appenders similar to the way 
the default.logging.conf was earlier.

> OpenEJB server prints logging messages to console.
> --------------------------------------------------
>
>                 Key: OPENEJB-667
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-667
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: general
>            Reporter: karan singh malhi
>         Attachments: openejb-667.patch
>
>
> Standalone server prints logging messages to the console. Need to append 
> messages to logs/openejb.log and logs/transaction.log

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to