Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-1590

Module logging and log4j.xml

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Could
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: OpenMRS 1.3.0
    • Component/s: Module Engine
    • Labels:
      None

      Description

      I doesn't look like 1) will work. Thanks anyway.

      Tammy

      Ben Wolfe wrote:
      > The log4j.xml included in your module doesn't get loaded/copied over to the webapp when loaded.
      >
      > I see two ways of achieving this:
      >
      > 1) get your module's log4j into the classpath and hope that the logging mechanism picks it up. Try putting your file into either the lib folder or change your build.xml so that the log4j.xml file is included in the root of your omod/jar file.
      > 2) change the module loading hierarchy to look at and read the log4j file and copy its contents into some other log4j file. (similar to how either messages.properties or dwr.xml are done)
      >
      > Ben
      >
      > Tammy Dugan wrote:
      >> I read the information on the wiki about how to get logging to work with my unit tests and everything is working great. However, I want my module to create a custom log file through the openmrs webapp as well which it doesn't. Do I have to edit the actual log4j.xml that goes with openmrs or is there some configuration where I can just include a log4j.xml in the omod file that will override the openmrs logging?
      >>
      >> Thanks,
      >>
      >> Tammy

        Attachments

          Activity

            People

            Assignee:
            bwolfe Ben Wolfe
            Reporter:
            bwolfe Ben Wolfe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: