Tapestry
  1. Tapestry
  2. TAPESTRY-1191

Misreporting Script component "scriptPath" property

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 4.0.2
    • Fix Version/s: 4.1.1
    • Component/s: Framework
    • Labels:
      None

      Description

      1. When the "scriptPath" is mistakenly applied to an inline Script component (<script jwcid="@Script" scriptPath="javascript.script" ...), Tapestry throws an org.apache.hivemind.ApplicationRuntimeException with the following message: "Either the scriptAsset or the scriptPath parameter must be supplied, neither parameter was set."

      "scriptPath" is supposed to be "script", as noted in the following JIRA issues:

      https://issues.apache.org/jira/browse/TAPESTRY-972
      https://issues.apache.org/jira/browse/TAPESTRY-963

      2. Incidentally, http://tapestry.apache.org/tapestry4/tapestry/ComponentReference/Script.html is also still reporting that the Script component has a "scriptPath" property.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Jim Steinberger
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development