[
https://issues.apache.org/jira/browse/WICKET-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612608#action_12612608
]
Pas Filip commented on WICKET-1747:
-----------------------------------
I'd like to propose this alternative for people who're developping wicket
applications using spring.
It has the advantage that the webpage's springbeans will be injected and
available in the constructor and that the spring bean fields are cleared before
serialization and reinjected after deserialization. It also avoids having to
proxy all of the services to avoid serialization issues.
It's not a final version yet but I'd like to know if this kind of concept could
be added to the project?
> Alternative to manage spring beans for a webpage
> ------------------------------------------------
>
> Key: WICKET-1747
> URL: https://issues.apache.org/jira/browse/WICKET-1747
> Project: Wicket
> Issue Type: New Feature
> Reporter: Pas Filip
> Attachments: SpringEnabledWebPage.java
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
