Tapestry 5
  1. Tapestry 5
  2. TAP5-140

The services used to handle live reloading should be made public

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.1.0.0
    • Component/s: None
    • Labels:
      None

      Description

      User services should be able to register for check-for-updates and/or invalidation event notifications without having to use any Tapestry internals. Firing such events should still be private/internal.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        May involve some new marker annotations to distinguish between class, template and message catalogs (for object invalidation events).

        Show
        Howard M. Lewis Ship added a comment - May involve some new marker annotations to distinguish between class, template and message catalogs (for object invalidation events).
        Hide
        Howard M. Lewis Ship added a comment -

        Note: document the services and/or annotations.

        Show
        Howard M. Lewis Ship added a comment - Note: document the services and/or annotations.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development