Tapestry 5
  1. Tapestry 5
  2. TAP5-220

Store the application servlet filter name into the context to let third party library follow the convention-over-configuration pattern.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Won't Fix
    • Affects Version/s: 5.1.0.0
    • Fix Version/s: 5.1, 5.0.18
    • Component/s: None
    • Labels:
      None
    • Environment:
      Any

      Activity

      Hide
      Massimo Lusetti added a comment -

      As per Howard's comments there's an easy workaround so if anyone feel strong about this it can reopen the issue.

      Show
      Massimo Lusetti added a comment - As per Howard's comments there's an easy workaround so if anyone feel strong about this it can reopen the issue.
      Hide
      Massimo Lusetti added a comment -

      I found it handy since more and more often i use this convention but i definitely can live without it using the workaround you suggested.

      Show
      Massimo Lusetti added a comment - I found it handy since more and more often i use this convention but i definitely can live without it using the workaround you suggested.
      Hide
      Howard M. Lewis Ship added a comment -

      Given that, even in 5.0, the Registry is stored using a well-known context attribute name, is this change required?

      Show
      Howard M. Lewis Ship added a comment - Given that, even in 5.0, the Registry is stored using a well-known context attribute name, is this change required?
      Hide
      Massimo Lusetti added a comment -

      The workaournd is nice. Cool you've marked this for 5.1 releases.

      Show
      Massimo Lusetti added a comment - The workaournd is nice. Cool you've marked this for 5.1 releases.
      Hide
      Howard M. Lewis Ship added a comment -

      I think a workaround is to get the Registry (it is attribute "org.apache.tapestry5.application-registry" in the ServletContext), get the SymbolSource service, and get the symbol InternalConstants.TAPESTRY_APP_NAME_SYMBOL.

      Show
      Howard M. Lewis Ship added a comment - I think a workaround is to get the Registry (it is attribute "org.apache.tapestry5.application-registry" in the ServletContext), get the SymbolSource service, and get the symbol InternalConstants.TAPESTRY_APP_NAME_SYMBOL.
      Hide
      Massimo Lusetti added a comment -

      Patch against current trunk

      Show
      Massimo Lusetti added a comment - Patch against current trunk
      Hide
      Massimo Lusetti added a comment -

      Patch against current trunk

      Show
      Massimo Lusetti added a comment - Patch against current trunk

        People

        • Assignee:
          Unassigned
          Reporter:
          Massimo Lusetti
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development