Query query = session.createQuery("from Jobs as j"); in Hibernate runs smoothly, but in Hibernate 3 doesnot run.
I use eclipse create two projects, one used hibernate2 the other used hibernate 3. Both projects codes are the same, except the jar files in lib.
I have no ideas about it , is there some gentlemen konwing the reason.
Thank a lot.

Exception?
Mapping files?

Best regards
Sven

Yes something wrong in Jobs.hbm.xml.
<hibernate-mapping package="com.testHib">

<class name="com.testHib.Jobs" table="jobs">
<id name="jobId" column="job_id" type="short">

</id>
Thanks for sven.
But I find another problem.
The page 'showdata.jsp' which displays some columns of 'Table Jobs' displays normally.
But if I refresh this page twice, it will throws Exception. Tomcat says cannot obtain the connection.
Is someone knowing the reason?

Exception?
Mapping files?

This time, show the stack trace of the exception. Show the whole mapping file.

Your "mapping file" appears to follow the older 2.0 DTD. We'd know for sure had you posted the whole thing. This is because the column is specified as an attribute of id, rather than a child element.

Exception:
Hibernate ExceptionNot able to obtain connection

com.testHib.Jobs

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

<!-- DO NOT EDIT: This is a generated file that is synchronized -->
<!-- by MyEclipse Hibernate tool integration. -->
<!-- Created Wed Sep 07 11:47:04 CST 2005 -->
<hibernate-mapping package="com.testHib">

<class name="Jobs" table="jobs">
<id name="jobId" column="job_id" type="short">

</id>

<property name="jobDesc" column="job_desc" type="string" not-null="true" />
<property name="minLvl" column="min_lvl" type="short" not-null="true" />
<property name="maxLvl" column="max_lvl" type="short" not-null="true" />

<!-- <set name="employeeSet" inverse="true">
<key column="job_id"/>
<one-to-many class="Employee"/>
</set>
-->
</class>

</hibernate-mapping>

hibernate.cfg.xml:

<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">

<!-- Generated by MyEclipse Hibernate Tools. -->
<hibernate-configuration>

<session-factory>
<property name="myeclipse.connection.profile">dbconn1</property>
<property name="connection.url">
jdbc:microsoft:sqlserver://server2;DatabaseName=pubs
</property>
<property name="connection.username">user</property>
<property name="connection.password">user</property>
<property name="connection.driver_class">
com.microsoft.jdbc.sqlserver.SQLServerDriver
</property>
<property name="dialect">
org.hibernate.dialect.SQLServerDialect
</property>
<property name="show_sql">true</property>
<mapping resource="com/testHib/Authors.hbm.xml" />
<mapping resource="com/testHib/Jobs.hbm.xml" />


</session-factory>

The most likely situation is that each time you refresh the page, you are opening a connection but not closing it, starving the connection pool. Make sure you are closing the Session and disregard anything I said earlier about the validity of the XML .

Thanks dennisbyrne very much.
You are right. I do close the session by the method (session.close();), but not close the sessionfactory.
Now it runs normally, thanks you again.

Uhm ... sessionFactory.close() is probably not a good idea.



Well, log back in and rate the post as helpful then.