Grails
  1. Grails
  2. GRAILS-8383

If a hibernate error occurs in an integration test, tearDown that does any GORM cleanup causes another hibernate exception re: not flushing if exception occurred

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0-RC2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      null id in org.weceem.html.WcmHTMLContent entry (don't flush the Session after an exception occurs)
      org.hibernate.AssertionFailure: null id in org.weceem.html.WcmHTMLContent entry (don't flush the Session after an exception occurs)
      	at org.weceem.services.ContentRepositoryServiceTests.tearDown(ContentRepositoryServiceTests.groovy:201)
      

      Happens after the failure (in the same test) as GRAILS-8381 running Weceem plugin integration tests

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Marc Palmer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Last Reviewed:

              Development