Hi there

I am wondering if the following is possible and also good practice.

My idea is to produce a single hibernate API jar that would be made available to any application wishing to access our db applications This seems to make sense on a design/maintence level.

My problem was how to make all mapping documents available to the hibernate API.

Would I have to reference all jars wishing to make use of the API on the classpath and then manually add all of the mapping resources to the API cfg.xml document? Is there a more dynamic way off approaching this?

Is there a mapping resource of sorts? Ie in a project can I group together all mapping resources requiurd for that development and then make this single resource available to the Hibernate API?

Any advice or a nudge in the direction of any reading material on this is greatly recieved

Thanks

Chris

I believe if you use "Configuration.addResource(Class c)" Hiberate will try to look for the Mapping XML in the same location as the Class file (i.e. in the fully qualified path of the class".

So for e.g. let's say you had a class whose name was foo.bar.Persist1

Then if you do

config.addResource(foo.bar.Persist1.class);

Hibernate will look for the XML file at:

<CLASSPATH>/foo/bar/Persist1.hbm.xml

Hope that helps.

Thanks for that. I was hoping for something a bt more generic.

I.e add a resource from the classpath that contains all of mappings for a sperate project rather than a reference to each individual mapping file.

Is it bad practice to have a single session manager for all projects to use but for each project to have its own hibernate.cf.xml document containing its own connection, properties and mapping profiles? Would this cause any problems?

Any help on this is welcome. There doesnt seem to be any documentation on this subject.

Thanks to tenwits answer on another post I have managed to solve this issue.

It appear you can use a <mapping jar=foo.jar> tag to import all of the *.hbm.xml documents from a given jar.