Comments on: Beware the non-namespaced classpath resource http://blog.markturansky.com/archives/37 software architecture & engineering, code hints, sometimes philosophy, photography, life, etc. Wed, 07 Jul 2010 08:09:58 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Mark Turansky http://blog.markturansky.com/archives/37/comment-page-1#comment-177 Mark Turansky Sun, 17 Feb 2008 05:09:03 +0000 http://blog.markturansky.com/archives/37#comment-177 Exactly right. Two projects by two different teams and there's my team attempting an integration effort. It took a lot of digging to figure this out, but now we know. I'll put a notch in the "experience" part of my brain. Exactly right. Two projects by two different teams and there’s my team attempting an integration effort. It took a lot of digging to figure this out, but now we know. I’ll put a notch in the “experience” part of my brain.

]]> By: Matt Passell http://blog.markturansky.com/archives/37/comment-page-1#comment-175 Matt Passell Sun, 17 Feb 2008 03:57:40 +0000 http://blog.markturansky.com/archives/37#comment-175 Let me guess... since each of the JARs has a hibernate.cfg.xml at the top level, it was picking up the first one in the classpath it found. Yup, namespaces can be handy for avoiding such conflicts. :) Let me guess… since each of the JARs has a hibernate.cfg.xml at the top level, it was picking up the first one in the classpath it found. Yup, namespaces can be handy for avoiding such conflicts. :)

]]>