[jira] Resolved: (WICKET-2370) LoadableDetachableModel sets attached true even when exception occurs during load()

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

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

Igor Vaynberg resolved WICKET-2370.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Igor Vaynberg

LDM is a very simple class, if it doesnt do what you want just roll your own.

> LoadableDetachableModel sets attached true even when exception occurs during load()
> -----------------------------------------------------------------------------------
>
>                 Key: WICKET-2370
>                 URL: https://issues.apache.org/jira/browse/WICKET-2370
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-RC7
>            Reporter: Antony Stubbs
>            Assignee: Igor Vaynberg
>
> LoadableDetachableModel sets attached true even when exception occurs during load(). We rely on exceptions being thrown / caught for our caching system, which in this case sits behind our LDM. Problem occurs on 2nd load attempt (where cache would now be populated), LDM returns null because the attached flag is still true.
> <code>
> 	public T getObject()
> 	{
> 		if (!attached)
> 		{
> 			attached = true;
> 			transientModelObject = load();
> </code>
> Locally, I will solve this for us by overriding getObject in a custom LDM which will either reorder the calls i.e.
> 			transientModelObject = load();
> 			attached = true;
> or, catch the caching exception and set attached to false.
> I admit this is debatable behaviour though. Thoughts?

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