6 Replies Latest reply on Mar 10, 2005 2:57 PM by Dan Thompson

    just venting on 3.2.6 port

    Dan Thompson Newbie

      starting the 4th day into our 3.2.6 port. nasty classpath issues, probably our own fault. loggers not resolving, too many versions of commons etc. just venting here, looking for a friendly ear (no pun intended).

      if anyone has any clear ideas about how to identify why log factory is not found it would be appreciated. we know that it is a class path / ant class loader issue, and that there are probably conflicting versions of various apache loggers, of but we've had our best and brightest working on it for a while. it could be that xdoclet is fighting with tomcat 5, or that log4j versions are out of date, or who knows what. we just don't have a clear plan of attack. if we understood a method of how to resolve the problem we could proably resolve it. but for now, it is just... try removing this jar... try removing that jar... just when we think we've got one part of the system buidling, another part breaks. c'est le pire!

        • 1. Re: just venting on 3.2.6 port
          Dan Thompson Newbie

          The apache logger doc says that this maybe a new "feature"

          If the isAssignableFrom() test fails because there is more than one instance of org.apache.commons.logging.Log visible in the class loader hierarchy, make the exception message that is reported explicitly state this, rather than the potentially misleading claim that an implementation class does not implement Log.

          However, trying to figure out where more than onle instance of Log might be visible is a difficult task.

          • 2. Re: just venting on 3.2.6 port
            Dan Thompson Newbie

            I am also relatively certain that there is only one copy of the class in any of the jar files in the class path... that is,
            org.apache.commons.logging.Log only exists in the commons-logging.jar found in the jbossweb-catalina.sar.

            • 3. Re: just venting on 3.2.6 port
              Dan Thompson Newbie

              OK, it might be that ANY class that implements Log. So now I'm thinking that maybe the cataina/common-el.jar has a logger... and that this might be the culprit?

              • 4. Re: just venting on 3.2.6 port
                Dan Thompson Newbie

                now we find that if we drop the commons-logging.jar into the ant/lib dir, the darned thing works. what is up with that? shouldn't have to place commons-logging there.

                • 5. Re: just venting on 3.2.6 port
                  Dan Thompson Newbie

                  OK, we;ve put our heads together and decided that this is our work around, to drop commons-logging.jar into the ant/lib folder. now we can build everthing again, and go on to start testing our 3.2.6 port.

                  • 6. Re: just venting on 3.2.6 port
                    Dan Thompson Newbie

                    The boiled down, simplest example of this problem is to do a jasper task followed by a webdoclet task in ant. we've taken out all the other cruft. just those two remain.

                    Seems to be an xdoclet issue. looks like it fights with jasper for the Log instance. we made sure that we were updated to xdoclet 1.2.2, made sure that we have the right and proper versions of all jars of this and we get a different error. so our xdoclet was not up to date. but now that it is, we still get failures.

                    We're still telling our developers to drop commons-logging into their ant/lib folder as a work-around.