Hi,
I'm getting a NullPointerException when I try:
Configuration config = new Configuration.addJar("commonDomain.jar");

commonDomain.jar is in the java.class.path

I must be doing something stupid - can anyone give me an example of how to use Configuration.addJar?

Thanks,
ct

>> commonDomain.jar is in the java.class.path

I am guessing you mean to say commonDomain.jar is part of the classpath. For example, say you have commonDomain.jar in the directory /java/lib.

If your classpath entry is /java/lib/commonDomain.jar, then the jar file is not on the classpath, it is part of the classpath.

If however, your classpath entry is /java/lib, then it is on the cklasspath and new Configuration.addJar("commonDomain.jar"); should work.

You guess correctly. My bad.

I need commonDomain.jar to be part of the classpath, but I also need a simple way of loading the hibernate mappings contained in it. It look's as if this isn't as simple as I initially hoped it would be.

How would you do this?

Project A:
- Core project with domain objects and hibernate mappings.

Project B:
- Another project with it's own domain objects and hibernate mappings that also needs to make use of the domain objects in project A.

ct

I only know "hack" sort of ways to do this.

Here's one:

This is how I'm doing it.

My Ant build.xml puts all my cfg.xml files in hibernate.cfg.jar and builds a hmb.jar for each database. Then my EAR file has

/hibernate.cfg.jar
/Ingres.hbm.jar
/Oracle.hbm.jar
/hibernate2.jar
/otherlibs.jar
/ejb.jar

Forgot about this piece. Each *.cfg.xml inside hibernate.cfg.xml has its mapping defined similar to this:

<mapping jar="Ingres.hbm.jar"/>
or
<mapping jar="Oracle.hbm.jar"/>

What's the difference between Oracle.jar and Ingres.jar - surely the hibernate mapping files are the same regardless of the underlying database?

Will <mapping jar="commonDomain.jar"/> only find hbm.xml files in the root of the jar, or will it recurse the contents of the jar looking for hbm.xml files?

Thanks,
ct

I probably could put all of my mappings in the same jar. I never really considered that. I just did it that way to logically group them together.

Also, the mapping section of the config xml is required, so I have to put something there in each one. If the mapping section was optional, I'd probably load everything together in 1 jar programatically. I suppose I could specify an empty jar in the config xml, then after all of the databases are configured load everything with a Configuration.addJar(jarName), but that's a nasty hack.