hibernate-mapping

I have created a view which will be used for fetching the data only(readonly) View : Grid_View > My Hibernate hbm file <hibernate-mapping> <class name="hibernate.domain.View" table="Grid_View" mutable="false"> <property name="ACCT_BR_CD" type="string"> <column name="ACCT_BR_CD"/> </property> <property name="ACCT_NO" type="string"> <column name="ACCT_NO"/> </property> <property name="LGL_ENTY_NM" type="string"> <column name="LGL_ENTY_NM"/> </property> <property name="CUST_CTRY_CD" type="string"> <column name="CUST_CTRY_CD"/> </property> <property name="ACCT_SRC_SYS_CD" type="string"> <column

I have two POJO's ,STOCK and STOCK_DETAILS (one to many relationship). Also I have one interface IAUDITLOG (having two methods). I need to implement this interface with BOTH POJO's and want to write some implementation within those methods. But when I implement IAUDITLOG interface with child class "STOCKDETAILS" then it gives exception "that you should have setter property" STOCK CLASS: @Entity @Table(name = "stock") public class Stock implements java.io.Serializable, IAuditLog { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) @Basic(optional = false) @Column(name = "id") private

I am having problems removing another entity through cascade delete-orphan. It works when I clear the associated set collection, but not when I make the set collection null. Let me explain in detail. The config snippet: <class name="com.sample.CategoriesDefault" table="cats"> <id name="id" column="id" type="string" length="40" access="property"> <generator class="assigned" /> </id> <version name="version" column="objVrs" unsaved-value="negative"/> <set name="bla" lazy="false" cascade="all-delete-orphan" inverse="true"> <key column="idCats" not-null="true"/> <one-to-many class="com.sample.BLA"/

I found in some old code strange thing (at least for me). The field which is annotated @ManyToOne is also annotated with @BatchSize . I always thought that @BatchSize annotation only affects when annotated at class level or on a collection ( @OneToMany ) and affects pre-fetching when iterating. But maybe I am wrong and annotating @ManyToOne with @BatchSize affects something. I can't find the answer in the documentation. Does annotating @ManyToOne with @BatchSize have sense? @ManyToOne associated with @BatchSize could make sense only if the corresponding field is marked as lazy ( lazy=true ).

I got a problem with a many to many association in my persistence layer. My scenario is the following: A user can has several roles and a role can have several user attached to it. During the tests I encountered a strange behavior. I created role object and several user objects. The role was set to each of the users. After this the users were saved using a DAO. Then one of the user gets loaded to check whether he got the role that was passed to him before saving the user object. Calling getRoles() on the user shows that the role was set correctly. To check whether the inverse direction also