Uploaded image for project: 'The AndroMDA project'
  1. The AndroMDA project
  2. ANDROMDA-1519

Log4j configuration for Cartridge ( template engine ) via log4j.xml

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      AndroMDA-3.0M2
      Windows XP Prof
      JDK : j2sdk1.4.2_05
      UML Tool : MagicDraw 7.8

      Description

      We have built a customized cartridge on andromda-ejb-cartridge-3.0M2. The other change we have is, we dont kill the JVM after every run of the generation. We have noticed that the log file generated for the template engine, keeps on growing, i.e the logs are appended to the file on every run.

      The VelocityTemplateEngine class has its own FileAppender, the appender added to logger is not configured for NOT appending the logs to the file.

      Moreover, its also not possible to configure the logging behaviour for this appender using the log4j.xml configuration file

      Also it would be nice to have the log4j.xml file picked up from some external dir, say using some System Property of the VM, this way it becomes handy for the developers developing customized cartridge as, they won't have to muck around with the library supplied by AndroMDA Team.

      Same implementation could be also be carried out for Cartridge-Rules.xml

        Attachments

          Activity

            People

            • Assignee:
              overheat overheat
              Reporter:
              vbn Vikram Naik
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: