best practices: logging in an osgi environment

Discussion in 'Java' started by brindy, Aug 25, 2007.

  1. brindy

    brindy Guest

    hi all,

    i am curious as to people's opinions of best practices regarding
    logging in an osgi environment.

    do you use java logging?

    or do you track the osgi log service?

    or do you use log4j? and if so, how do you package it and declare
    dependancies to it (e.g. package-import or require-bundle?)

    ideally, i'd like to keep my code decoupled from the osgi framework,
    so that means creating abstraction for the log service api (not
    another logging api?!) or simply not using it all. java logging seems
    like a logical thing to use as it is there in the api and ready to
    use... but how does it operate in an osgi environment and what kind of
    control do i have over it?

    any advice gratefully received

    cheers,
    brindy
     
    brindy, Aug 25, 2007
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. herc
    Replies:
    0
    Views:
    378
  2. Andreas Wapf

    python & osgi

    Andreas Wapf, Sep 13, 2007, in forum: Python
    Replies:
    1
    Views:
    714
    Marc 'BlackJack' Rintsch
    Sep 13, 2007
  3. Schwede
    Replies:
    0
    Views:
    382
    Schwede
    Oct 29, 2007
  4. Hoss Spence

    Testing your logging (best practices)

    Hoss Spence, Feb 7, 2008, in forum: Java
    Replies:
    1
    Views:
    309
    Roger Lindsjö
    Feb 9, 2008
  5. Rhino

    Logging - Best Practices

    Rhino, Apr 29, 2010, in forum: Java
    Replies:
    4
    Views:
    459
    Martin Gregorie
    May 1, 2010
Loading...

Share This Page