Tapestry
  1. Tapestry
  2. TAPESTRY-2033

Optimized requests paths are broken for root paths within contexts

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.8
    • Fix Version/s: 5.0.8
    • Component/s: None
    • Labels:
      None

      Description

      TAPESTRY-1502 changed the way that URLs were generated. The comments on the issue indicate it works great for a non-root context, but my experience is indicating otherwise. It is possible I've done something wrong, but without changing a single line of code, all of my pagelinks, actionlinks, includescripts, includestylesheets, and so forth have broken.

      In this case, I have my app mapped to the "/manager" context. I access it locally via http://localhost:8080/manager/.

      The generated URLs are all of the form:

      <script src="manager/assets/scriptaculous/prototype.js" type="text/javascript"></script>

      As you can see, the context is being included in the path but done so relatively. The above would resolve to http://localhost:8080/manager/manager/assets/scriptaculous/prototype.js, which is incorrect. It should be http://localhost:8080/manager/assets/scriptaculous/prototype.js

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Kevin Menard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development