I've found in an hibernate.cfg.xml example, the following line:

<mapping package="toto">

No doc about it, What does it mean ?

I've seen another example with the package keyword :

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 2.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">

<hibernate-mapping package="toto">
<class name="Foo" table="FOO">
<id name="key" column="FOO_KEY" type="long">
<generator class="sequence">
<param name="sequence">FOO_GEN</param>

Can you explain a little bit ?

Thank you.
Richard

It defines a java-package namespace in effect for that <hibernate-mapping/>. Meaning, within that mapping declaration you do not need to fully qualify your domain class class-names *if* they are within that package.

Say I have a class with FQN "foo.Bar". In my mapping, I could either say:

- or -


It also applies to assocation mappings. Say I also have "foo.Baz":

- instead of -


Its just a way to save typing

Ok, I understand it as a convenient method but you didn't write about the following case :

<hibernate-configuration>
<session-factory>
<property name="connection.datasource">java:/comp/env/jdbc/annuaire</property>
<property name="dialect">org.hibernate.dialect.PostgreSQLDialect</property>
<property name="show_sql">false</property>

<mapping package="test"/>
<mapping class="test.Flight"/>
<mapping class="test.Sky"/>
<mapping class="test.Person"/>
<mapping class="test.animals.Dog"/>
</session-factory>
</hibernate-configuration>

What it the actual meaning of <mapping package="test"/> ? I bet it's annotation related ....

oh, sorry did not notice you were talking about the cfg.xml...

Yes, that tells Hibernate about a package containing annotated classes

http://www.hibernate.org/hib_docs/annotations/

Do I include the mapping package entry in the hibernate.cfg.xml only if I have a package level annotation (for example, a GenericGenerator)?

I did read this thread and the doc referred to in the last entry, and I see the example with a mapping package entry, but I do not see it say what that entry provides.

I was hoping that adding the mapping package entry meant that I do not have to add an individual mapping class entry for each annotated class within that package. This does not seem to be the case, and I am wondering if someone can confirm this.


Here is my config that works:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration
PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">

<hibernate-configuration>
<session-factory>
<mapping resource="Class1_hbm.xml"/>
<mapping resource="Class2_hbm.xml"/>

<!-- list of annotated packages and classes -->
<mapping package="com.ieminc.example.domainobjects"/>
<mapping class="com.ieminc.example.domainobjects.Class3"/>
<mapping class="com.ieminc.example.domainobjects.Class4"/>
<mapping class="com.ieminc.example.domainobjects.Class5"/>

</session-factory>
</hibernate-configuration>


Here is my 'hoped for' config that does not work:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration
PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">

<hibernate-configuration>
<session-factory>
<mapping resource="Class1_hbm.xml"/>
<mapping resource="Class2_hbm.xml"/>

<!-- list of annotated packages and classes -->
<mapping package="com.ieminc.example.domainobjects"/>
<!-- comment out classes that are in the package already specified -->
<!--<mapping class="com.ieminc.example.domainobjects.Class3"/>-->
<!--<mapping class="com.ieminc.example.domainobjects.Class4"/>-->
<!--<mapping class="com.ieminc.example.domainobjects.Class5"/>-->

</session-factory>
</hibernate-configuration>


In all examples I have seen on Hib site and in internet searching, there is always at least one class entry mapped within the package already mapped, which leads me to believe that my idea is wishful thinking.

Have just begun on Hib2 to Hib3 migration, and starting on Annotations. Go Hibernate!

Thank you,
Jeff

You are correct, this is not the case. I have clarified the wording in the documentation. What you ask for is not really useful since the archive is scanned for all @Entity classes anyway

Emmanuel,

Thank you for the response and for mentioning the archive scan for @Entity classes. I was not aware of that and I am looking into that now. I appreciate it!

Jeff