Women in Technology

Hear us Roar



Article:
  Understanding Classloaders: log4j in a J2EE Environment
Subject:   this is not an o'reilly quality article
Date:   2003-04-10 21:55:40
From:   anonymous2
i get the feeling this article wasn't proofread by anyone that really writes java.
Full Threads Newest First

Showing messages 1 through 3 of 3.

  • this is not an o'reilly quality article
    2003-04-11 05:31:57  gvix [View]

    Hello,

    Could you please elaborate as to why you think this was not an O'Reilly quality article?

    Regards,
    Vikram Goyal
  • this is not an o'reilly quality article
    2003-04-15 02:36:45  anonymous2 [View]

    I do not know what is O'Reilly Quality sepcifications. But I did not understand the purpose of writing this article. If it is regarding class-loaders, the author says, it is big topic, and is outside the scope. If it is regarding J2EE-log4j integration, I think not even 20% of the issues of log4j in J2EE application are discussed (Clustering, Multiple weblogic instances on single machine, EJB and web app deployed separate etc. etc) More than 30% of the text is on setup of weblogic-log4j. The author has given a link to Weblogic class-loader mechanism, which is very much self explanatory.

    So please anybody tell me what is this article for ???

    • this is not an o'reilly quality article
      2003-04-17 20:41:07  gvix [View]

      Hello,

      The intent of the article was to specify the classloading problems for log4j integration in a J2EE environment. It was neither solely about classloaders nor solely about log4j in a J2EE environment. It was addressing a specific problem.

      Regards,
      Vikram Goyal