Hibernate disable collection fetching -

Use the latest Hibernate 3 ...

is a model where element class has 2 List store is the relation class, the place where the element owner (sources) is concerned and second when it is the destination.

  & lt; Class name = "Element" .... & gt; .... & lt; List name = "source reference" .... & gt; ... & lt; One-to-many classes = "... relationship ..." & gt; & Lt; / List & gt; & Lt; List name = "Destination correction" .... & gt; ... & lt; One-to-many classes = "... relationship ..." & gt; & Lt; / List & gt; & Lt; / Square & gt; & Lt; Class name = "relationship" .... & gt; .... and lieutenant; Many-to-one names = "source" class = "... element ..." ... column name = "SOURCEID" sql-type = "INTEGER" no-null = "true" /> & Lt; / Many-to-one & gt; & Lt; Many-to-one names = "destination" class = "... element ..." ... column name = "DESTINATIONID" sql-type = "integer" no-null = "true" /> & Lt; / Many-to-one & gt; & Lt; / Square & gt;   
 Mapping is only useful when creating benchmark queries. Otherwise when I bring a element (only through the criteria, never received / load), I should be in hibernation to actually bring the relation collection. never. Right now in my code, I returned the Element object by creating a new element and clearing those properties before I transmit (i.e. the source transfer / destination relation has never changed). It also goes for the criteria query about relation objects that the source / destination property (i.e. element) is cleared.  
 Is there any way to force Element entities to pry through element unit through hibernate interceptor or to eliminate the basic element source / cellularization properties to use the tuplizer? / P>  
 
 
 What is the lazy = "true" to match the collection of relations, do not provide the desired behavior?  
 If it is not, then use alternative class succession. To use those elements, there should be a base class of the base class of the element, which is being used in cases where you can modify the data that you have returned, and then a subclass that stores the collection Adds when you need a large amount of data.