I'm having some wierd behavior in which saveOrUpdate does not actually save my changes back to the database and no exceptions are thrown. Im not sure what exactly is going on. Here is my Hibernate Mapping file for the Object in question:

<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping>
<class name="com.tite.medicalworks.server.security.Role" table="roles">
<id name="ID" type="long" column="id">
<generator class="native"/>
</id>

<property name="name" type="string" unique="true"/>
<property name="description" type="string"/>

<map name="accessMatrix" table="role_category_access" inverse="false" order-by="category_id" cascade="all" lazy="false">
<key column="role_id"/>
<map-key column="category_id" type="int"/>
<element column="access_level" type="int"/>
</map>

</class>
</hibernate-mapping>

----------------------------------

I'm not sure what im doing wrong, but I call session.saveOrUpdate(someRole); and it doesn't update the DB. I resorted to making HQL calls for each field:

session.createQuery("update Role set name = '" + role.getName() + "' where id = " + role.getID()).executeUpdate();

session.createQuery("update Role set description = '" + role.getDescription() + "' where id = " + role.getID()).executeUpdate();

HOWEVER, when it came to the map in the Role object I tried to make sql calls to save the relationships and of course I reliazed executeUpdate for createSQLQuery was not supported. as it throw an exception. So Im not sure how to save back the mapping to the database at this point since hibernate refused to do it on its own. Its loads the roles fine, and saveOrUpdate works fine for other objects, im not sure why it doesn't for this particular class.

Any help would be much welcome!

O yea, its very wierd because delete works, all mappings are removed so I'm not sure why saveOrUpdate is not working

Hibernate tries to minimize DB access. Did you commit the hibernate transaction? Or call flush() on the session?

Thanks for the response, yes I thought that might be the problem and I called flush with no success. The transaction is being managed by JBoss, so it should be committing the transaction. I am just perplexed because when I use HQL to save each field explicitly, it works.

yes you have to commit transaction even in CMT env ...are you using slsb's ...how are you managing your transactions...???