Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-403

OneShotLock tests fail under JDK 1.6 because of JVM differences

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.1.0.0, 5.0.18
    • 5.1.0.0
    • tapestry-ioc
    • None

    Description

      The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock

      As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of
      Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however,
      Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            andyhot Andreas Andreou
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: