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

HHH-4036: EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP 5.1.0 Post Release
    • Hibernate
    • None

    • JBoss EAP 5.1, JDK 1.6

    • Release Notes
    • Hide
      Hibernate Core EntityMetamodel entityNameByInheritenceClassNameMap field was used inconsistently. It used a class for puts to the map, but a method for gets from it. An exception was thrown when saving instances of subclasses with specific entity names. The EntityModel class has been updated to use class inheritenceClass instead of its getName() method. Saving instances of subclasses no longer causes an exception in these cases.
      Show
      Hibernate Core EntityMetamodel entityNameByInheritenceClassNameMap field was used inconsistently. It used a class for puts to the map, but a method for gets from it. An exception was thrown when saving instances of subclasses with specific entity names. The EntityModel class has been updated to use class inheritenceClass instead of its getName() method. Saving instances of subclasses no longer causes an exception in these cases.
    • Documented as Resolved Issue

    Description

      A inconsistent way of get entity name in org.hibernate.tuple.entity.EntityMetamodel causes "org.hibernate.HibernateException: Unable to resolve entity name from Class", if you have a different mapped name that class name in a joined subclass.

      This is a issue relationed with http://opensource.atlassian.com/projects/hibernate/browse/HHH-4036, it was fixed and need a back port to EAP version. Please look HHH-4036 for more information

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5749 CLONE - HHH-4036: EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              shaozliu Strong Liu(刘少壮) (Inactive)
              rhn-support-alazarot Alessandro Lazarotti
              Misty Stanley-Jones Misty Stanley-Jones (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: