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

It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.

      This is doable, but awkward and ugly, today.

      Ideally, this would be a matter of changing the web.xml mapping to:

      <url-filter>/t5/*</url-filter>

      and making some form of configuration change, i.e.,

      configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");

      This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.

      Of course, Websphere has some bugs in this area that might cause some grief.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              hlship Howard M. Lewis Ship
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: