Tapestry
  1. Tapestry
  2. TAPESTRY-1413

absolute classpath asset paths not found when no "classpath" specifier used

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 4.1.2
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      When using a path specifier like "/org/apache/tapestry/html/Shell.jwc" the classpath factory doesn't correctly return true for assetExists because it doesn't take into account whether the string given is an absolute or relative path.

        Activity

        Hide
        Jesse Kuhnert added a comment -

        Too much to get into, it works now.

        Show
        Jesse Kuhnert added a comment - Too much to get into, it works now.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Jesse Kuhnert
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development