[
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
Made the following changes:
1. Got rid of the init(), initialize() methods and the Log4jConfigUtils inner
class
2. On class load, it will configure logging. The logic is as follows (taken
from David Blevins' email)
- if conf/logging.properties exists, use it
- if conf/ directory exists, install logging.properties and use it
- else assume embedded and use embedded.logging.properties
(I did not explicitly look for the third step (embedded.logging.properties)
file, because this can be set through the log4j.configuration property when we
run tests. This way we still keep the flexibility on the filename during tests
, but we are a little more rigid with the user in that the user will have to
specify the logging config in the conf/logging.properties file.
> 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.
