In this example, SubComponent points to a Component. When I load a SubComponent, I get a proxy for the Component and it's not even initialized. I need the real class.


<?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">

<hibernate-mapping
>
<class
name="com.joe.SubComponent"
table="SUB_COMPONENT"
>

<id
name="id"
column="ID"
type="java.lang.Integer"
>
<generator class="sequence">
<param name="sequence">INTERNAL_ID_SEQ</param>
</generator>
</id>

<property
name="lastModifiedBy"
type="java.lang.String"
update="true"
insert="true"
column="LAST_MODIFIED_BY"
length="100"
not-null="true"
/>


<many-to-one
name="component"
class="com.joe.Component"
cascade="none"
outer-join="auto"
update="true"
insert="true"
lazy="false"
>
<column
name="COMPONENT_ID"
/>
</many-to-one>



</class>

</hibernate-mapping>

Using Hibernate 3.0.2

fetch="join"

fetch="join" didn't work.

I wasn't specific in how I load the object thinking it didn't (shouldn't) matter. In this case the object is being loaded using a org.hibernate.Query object. Using hsql:

select c from Component c where ...

Either put a

in the class tag of your Component if you never want to get a proxy.

Or call

in order to initialize a proxy in a particular situation.

HTH
Ernst

Try

to override

declared in Component.hbm.xml

Adding a class level tag - lazy="false" to Component works as expected. In my case, this is the perfect solution as it will generally pull the Component from second level cache any way, so there is no performance issue.

The join solutions (which I didn't fully try out) would seem to hinder performance because I don't need to read the Component from the db every time and I'll have hundreds of SubComponents attached to the same Component. ...just a thought.

Thanks all for your help!

It seems that it's trying to proxy everything including simple fields!? after upgrading to hibernate 3 and I would like to it behave like hibernate 2 did. Setting lazy="false" on the class fixes it, but that's a pain to go into all my entities and set that. Why does it proxy basic class fields?

ex:

23:10:02,351 ERROR LazyInitializationException:19 - could not initialize proxy - the owning Session was closed
org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed
at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53)
at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:80)
at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134)
at com.x.y.MyObject$$EnhancerByCGLIB$$5e1dd2b1.getAmountOnAccount(<generated>)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)