I’d just like the tout the WHICH4J Project which has helped me immensely in my classpath confict issues with Oracle over LOG4J and JAXB.

Which4J is a small utility jar that can be added to your classpath and used via:

System.out.println("WHICH 4J: "
+ Which4J.which(JAXBContext.class))

Works fine with WebSphere Application Server

Related Posts

• javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package {0}
• Adding pre-built JAR files to your EAR in Rational Application Developer
• Log4J “NoSuchMethodError” for org/apache/log4j/Logger.trace(Ljava/lang/Object;)V
• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB
• WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.