Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-3264

Don't use log4j configuration classes in our CXF tools - identify possible workarounds

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • jbossws-cxf-4.0.0.Beta2
    • None
    • None
    • None

      <opalka> dmlloyd, I found ugly dependency - http://fpaste.org/9UXj/
      <stuartdouglas> opalka: I actually hacked up something last night to try and find those problems
      <opalka> dmlloyd, stuartdouglas this is the call resulting to this dependency - we're using log4j configurators - http://fpaste.org/aKXp/
      <dmlloyd> why?
      <dmlloyd> (a) you shouldn't do that, (b) to fix the problem add "javax.api" to log4j's module dep
      <opalka> dmlloyd, this is question for alessio. I have no idea? Probably Alessio want's to use log4j config facility
      <dmlloyd> ok well if we're doing that it's pretty lame because we go through many hoops to avoid using the log4j config facility
      <opalka> dmlloyd, method javadoc isn't more descriptive as well - http://fpaste.org/DyVx/ I'll need to ask Alessio
      <opalka> dmlloyd, but just to confirm, we don't want org.apache.logging -> org.w3c.dom dependency in AS7, right ?

      • opalka don't like this dependency
        <dmlloyd> no, org.apache.logging is something completely different
        <dmlloyd> it should be org.apache.log4j -> javax.api
        <opalka> dmlloyd, and do we want this dependency ?
        <dmlloyd> yeah, it's fine to add
        <dmlloyd> but we don't want this manual log4j configuration

              rhn-support-asoldano Alessio Soldano
              ropalka Richard Opalka
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: