• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jsp and log4j priority control

 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
I came across a technique for utilizing the log4j logger within jsp scripts for providing diagnostic feedback.
I was hoping I could add, e.g.,


throughout my code for development level information and when ready for production, define the priority for the package to ERROR so such messages would no longer be logged without touching code. Seemed like a clean solution.
However, the priority rule doesn't seem to work with JSPs?
In order to determine the classpath for the compiled jsp I println out the this.getClass().getName() information of the jsp.
This came back as:
(cart being the class that was generated).

so I figured adding a rule like this:



would do the trick, but when set this way I still get debug level output. Is it possible to control the priority level logging of jsps? and if so, how?
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic