#Jboss tattletale trial#

Love or hate itвЂ¦ he will stay for a moment. PostSonarUnverifiedWebInfJars(unallowed.size())Д®nable the run of this scripts via maven plugin in a dedicated profile target/mywebapp-$ : undesired dependencies detected !' msg.toString() вЂ“ duplicate jars (often due to maven relocation) вЂ“ undesired dependencies like the one bundling javax.** classes To audit your web-inf/lib, jboss tattletale is THE tool to identify :

#Jboss tattletale trial#

I know that itвЂ™s ironic but this tool developed by JBoss will save you hours of trial and errors. To minimize the side effect of the bundled jars in websphere you setup the classloader policy of your application and module to parent last. To diagnose classloading issues like NoClassDefFound, Violation Constraint,вЂ¦ you can enable the verbose classloading. We are in 2012вЂ¦ osgi is there since a long time and IвЂ™m still struggling with websphere and its bundled xerces. If you have long running transaction like quartz job, test them extensively. If you plan to use jta transactions, and multiple datasources/queues, donвЂ™t forget to use XA transactions or tweak your transactions to avoid mixing access in a single transaction (and design it for possible data loss).ДЄlso reduce the isolation level through the datasource property webSphereDefaultIsolationLevel (the default one is repeatable read). You can use the spring profiles to lookup your datasource via jndi instead of using dbcp or another datasource implementation.

You probably want to keep your jetty/tomcat compliance and if you are in webphere switch to the specific implementation (jndi datasource, jta transaction manager,вЂ¦) If your client plan to use websphere, may be he wants to use the built-in websphere datasource, an implementation collecting various statistics about connection, prepared statement,вЂ¦ All is well and good on your jetty or tomcat servers, then one of your client want to deploy your application in websphere application server, and trouble begins