[
https://issues.apache.org/jira/browse/WICKET-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985314#action_12985314
]
Willis Blackburn commented on WICKET-3364:
------------------------------------------
I often call setDefaultModel in component constructors.
I don't have a specific use case; I don't have any StatelessLInks in my app.
I'm just thinking that model vs. no model and stateful vs. stateless are two
separate properties and that there's no compelling reason to require that
stateless links also have a Void model type--especially when they can have
models.
> StatelessLink should not force the model type to Void
> -----------------------------------------------------
>
> Key: WICKET-3364
> URL: https://issues.apache.org/jira/browse/WICKET-3364
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Willis Blackburn
> Priority: Minor
>
> StatelessLink is just a shortcut for a Link with the stateless hint set to
> true. I don't think that it should force the model type to Void. Sure, the
> model that existed at the time the link was created may be gone, but that
> doesn't mean that there is not another model available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
