This would be quite difficult to implement. Internally, a one-to-one property-ref looks nothing like a collection.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Sunday, November 20, 2005 2:28 AM To: Hibernate development Subject: [Hibernate] Second level cache and mappedBy side of a FK one-to-one Owner side <many-to-one name="person" class="Person" column="PERSON_ID" unique="true"/> mappedBy side <one-to-one name"employee" class="Employee" property-ref="person"/> In this case, the owner side is resolved in cache, and not the mappedBy side (if I load person, employee will be resolved in the 2nd cache, if employee is loaded, person cannot be resolved in the 2nd level cache) But the mapped by side is actually some kind of 1 element collection (in a true bidir many to one we can cache both sides. Would it make sense to allow caching of the mappedBy side with a same mechanism than the one used in collections? ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel