[
https://issues.apache.org/jira/browse/WICKET-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899592#comment-15899592
]
Sven Meier commented on WICKET-6334:
------------------------------------
> the model itself provide proper handling of concurrency
LoadableDetachableModel doesn't handle concurrency properly, it isn't meant to
be used concurrently (as all other models). Please check its #getObject()
implementation.
> And I'm just curious why is it forbidden to have a model within Session if
> it's properly handled?
I applaud your curiousity: models are for components, they are single threaded
(as are components) and thus have nothing to do within a Session.
> The issue is not about how to use session and models within Wicket but rather
> why this error appears in the log if model is being detached properly at the
> end?
As long as you haven't provided a valid use case, I can't make a statement on
why the error appears in the log.
> WicketObjects#sizeof() should detach Sessions
> ---------------------------------------------
>
> Key: WICKET-6334
> URL: https://issues.apache.org/jira/browse/WICKET-6334
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.6.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
>
> Report at users@ : http://markmail.org/message/mq5zs2veaj4q4psg
> Wicket should detach the Session before calculating its size as it does for
> Component and IDetachable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
