Tapestry 5
  1. Tapestry 5
  2. TAP5-955

Add @Optional annotation to mark contribution methods that can be ignored if the indicated service does not exist

    Details

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

      Description

      Currently the registry wil not start if a module makes contributions to a service which does not exist (e.g. because the module with the service is not loaded). This makes problems with applications, that allow installations with a subset of all modules started. A module should be able to contribute to an extension point only if it is available. In case the service does not exist, the contribution should be ignored.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Peter Rietzler
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development