Tapestry 5
  1. Tapestry 5
  2. TAP5-1123

Documentation in ApplicationStateManager is not quite correct: when creating an SSO it uses the full injection machinery, not necessarilly the no-args constructor

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.1
    • Labels:
      None

      Description

      /**

      • For a given class, find the SSO for the class, creating it if necessary. The manager has a configuration that
      • determines how an instance is stored and created as needed. A requested SSO not in the configuration is assumed
      • to be created via a no-args constructor, and stored in the session.
        *
      • @param <T>
      • @param ssoClass identifies the SSO to access or create
      • @return the SSO instance
        */
        <T> T get(Class<T> ssoClass);

      That's whats wrong, because it actually uses ObjectLocator.autobuild() now (since at least 5.1).

        Activity

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development