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

Some method names are not allowed in components and pages

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Invalid
    • 5.0.18
    • None
    • tapestry-core
    • None

    Description

      Some method names in components and pages make tapestry throw an Exception: "StackMapTable format error: bad class index". Howard assumes this is a naming conflict to methods tapestry adds to components and pages on the fly.

      This is an example method, that throws the exception:

      @BeginRender
      boolean render(MarkupWriter writer) {
      //blubb
      return false;
      }

      When i rename the method to "boolean blubb(MarkupWriter writer)" for example, everything is fine.

      In the stack trace one can not see which method it is, or in which page/component the naming conflict occurs. It would save one some time to find the corresponding component if the stack trace or the exception message would give one a hint.

      Attachments

        Activity

          People

            Unassigned Unassigned
            felixgonschorek Felix Gonschorek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: