ginal post.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an-ajax-call-tp3446979p3509490.html
Sent from the Users forum mailing list archive at Nabbl
to accept
> Serialisable
> instead of Long?
> Maybe I'm missing something basic here. But your suggestion helped to get
> past the initial hurdle.
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-de
t the initial hurdle.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an-ajax-call-tp3446979p3457227.html
Sent from the Users forum mailing list a
rson.class, personId));
> }
>
> I fear I'm missing a very small detail that's stopping me from having this
> working.
> Thanks, Lucas
>
>
>
> ------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http
.class, personId));
}
I fear I'm missing a very small detail that's stopping me from having this
working.
Thanks, Lucas
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an-ajax-call-tp3446979p3456789.
The 'implicit super constructor' warning means that in your constructor you
need to call 'super()'
The 'complains on type T' part I'd need a little more info. Feel free to
post the exact lines of code.
-Clint
On Sat, Apr 16, 2011 at 2:21 AM, lucast wrote:
> However, when I try to extend the Ab
and come back to it in a week's
time.
Thank you, Iain and @Clint for your posts. They are much appreciated.
Kind regards,
Lucas
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an-ajax-call-tp3446979p3453635.html
S
On Thu, Apr 14, 2011 at 3:51 PM, Iain Reddick
wrote:
> Firstly, that LDM code is broken - calling detach() on load() makes no
> sense.
>
Right - you should *not* call detach from within load().
> Also, it will hit hibernate on every call to getObject(), as you aren't
> caching the loaded Parent
Thank you, Iain.
I shall try that.
Cheers,
Lucas
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an-ajax-call-tp3446979p3450740.html
Sent from the Users forum mailing list archive at Nabble.com
-
From: "lucast"
To: users@wicket.apache.org
Sent: Wednesday, 13 April, 2011 7:20:15 PM
Subject: Re: Refreshing loadable detachable model object inside an ajax call
Hi Clint, thanks for your email.
After reading your post, this is how I've implemented the LDM class:
public
idn't get that right straight away. I have implemented it
as in the above example but when I call (Parent) model.getObject(); I get
the same exception as before.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Refreshing-loadable-detachable-model-object-inside-an
> Model is just the standard: parentService().load(Parent.class, id);
>
> How can I refresh the Loadable Detachable Model object without getting the
> above exception and without having to refresh the entire page?
>
>
> Any help will be greatly appreciated.
>
>
> --
-model-object-inside-an-ajax-call-tp3446979p3446979.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h
13 matches
Mail list logo
