[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

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.1
• Component/s: documentation, tapestry-core
• Assignee: Unassigned
• Reporter: Howard Lewis Ship
• Created: 29/Apr/10 18:26
• Updated: 05/Sep/10 21:49
• Resolved: 03/Sep/10 23:18

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).