You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2010/04/29 13:59:53 UTC

[jira] Resolved: (CLK-667) Spring servlet should support stateful pages with transient beans

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

Bob Schellink resolved CLK-667.
-------------------------------

    Resolution: Fixed

fix checked in

> Spring servlet should support stateful pages with transient beans
> -----------------------------------------------------------------
>
>                 Key: CLK-667
>                 URL: https://issues.apache.org/jira/browse/CLK-667
>             Project: Click
>          Issue Type: Bug
>          Components: extras
>    Affects Versions: 2.1.0
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.2.0
>
>
> SpringClickServlet currently injects beans only for newly created page instances. This works well for stateless pages but not for stateful pages that have been serialized/deserialized. After a stateful pages has been deserialized, the bean references are null.
> ClickServlet provides the #activePage hook which can be used to re-inject beans after deserialization.
> Unfortunately this fix will only apply to "Click created pages with bean injection" or option 3 described in the SpringClickServlet. Option 1 and 2, where Spring itself creates the Click pages and inject beans, does not work after deserialization because Spring does not re-initialize the page. Its possible to inject serializable proxies instead of direct references, however that could mean relying in byte code generation.

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