[jira] Closed: (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

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1123.
--------------------------------------

    Fix Version/s: 5.2.1
       Resolution: Fixed

> Documentation in ApplicationStateManager is not quite correct: when creating an SSO it uses the full injection machinery, not necessarilly the no-args constructor
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1123
>                 URL: https://issues.apache.org/jira/browse/TAP5-1123
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: documentation, tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Priority: Trivial
>             Fix For: 5.2.1
>
>
>     /**
>      * 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).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.