Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5765

HHH-5853 Problem loading cachable collections defined with a property-ref key with a versioned owner

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0
    • Fix Version/s: EAP_EWP 5.1.1
    • Component/s: Hibernate
    • Labels:
      None
    • Environment:

      EAP 5.1.0

    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide
      • Migrating away from property-ref and normalizing the data
      • disabling caching on the collection
      • disabling versioing on the owner
      • disabling versioning on the collection (<set ... optimistic-lock="false">)
      Show
      Migrating away from property-ref and normalizing the data disabling caching on the collection disabling versioing on the owner disabling versioning on the collection (<set ... optimistic-lock="false">)
    • Release Notes Text:
      Hide
      If an entity defined a collection with a property-ref-based key as cacheable, there was a problem loading the collection and putting it into its second level cache region. Hibernate used the incorrect key for the owning entity. It attempted to use the referenced property value instead of the corresponding ID value.

      Hibernate now checks whether the collection key is defined by a property-ref. If so, the key of the owner instance associated with the collection itself is used, if it exists. Hibernate resolves the owner of the collection against the owner of the Persistence Context.
      Show
      If an entity defined a collection with a property-ref-based key as cacheable, there was a problem loading the collection and putting it into its second level cache region. Hibernate used the incorrect key for the owning entity. It attempted to use the referenced property value instead of the corresponding ID value. Hibernate now checks whether the collection key is defined by a property-ref. If so, the key of the owner instance associated with the collection itself is used, if it exists. Hibernate resolves the owner of the collection against the owner of the Persistence Context.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      See http://opensource.atlassian.com/projects/hibernate/browse/HHH-5853

      ====================
      If an entity defines a collection with a property-ref based key as cacheable, there is a problem loading said collection and putting it into its second level cache region. The issue appears to be due to the incorrect "key" used to locate the owning entity; it tries to use the referenced property value instead of the corresponding id value.
      ====================

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                stliu Strong Liu
                Reporter:
                sjmenden Samuel Mendenhall
                Writer:
                Misty Stanley-Jones
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: