Re: bad practice in sharing models between wicket form and hibernate?

You shouldnt put that object directly in a CPM, but have a loadabled detachable model in between. Because now you probably have that hib object in the page between requests On 28/02/2009, Stephen Swinsburg s.swinsb...@lancaster.ac.uk wrote: Hi all, I'm after your thoughts on the following

Wicket - Multi Instance Support

Hi, Does wicket provide any support for multiple application instances per user's session? In other words, how does wicket handle multiple browser windows for the sample application. Thanks. -- View this message in context:

Re: bad practice in sharing models between wicket form and hibernate?

Let's say you have a Java object with 20 fields that's mapped to a database using Hibernate. I don't see that there's much difference in terms of memory utilization between using that object as the model and creating a separate object with 20 fields to use as the model. Following the

Re: bad practice in sharing models between wicket form and hibernate?

i didnt say you have to have a different object. I just say dont keep persistent objects in memory between requests. Use detachable for that. The only exception i guess is when you create a new object that isnt persisted yet to the db and you have some kind of wizard to fill it up. On Sun, Mar

Re: Multiple Forms in A Border

I found out that this exception only happened to Wicket-1.4. I tried Wicket 1.3.5 and it worked fine. I presume all Wicket 1.3.x works too. -- View this message in context: http://www.nabble.com/Multiple-Forms-in-A-Border-tp22252817p22273577.html Sent from the Wicket - User mailing list archive

Re: Multiple Forms in A Border

file a jira bug with a quickstart please. -igor On Sun, Mar 1, 2009 at 6:34 AM, TH Lim ssh...@gmail.com wrote: I found out that this exception only happened to Wicket-1.4. I tried Wicket 1.3.5 and it worked fine. I presume all Wicket 1.3.x works too. -- View this message in context:

Re: bad practice in sharing models between wicket form and hibernate?

Johan, I was trying to say, in a confused kind of way, that standard practice is to back a form up with a bean of some kind, and that replacing that bean with a persistent object wouldn't necessarily increase memory utilization enough to bother with a detached model. On the other hand

Re: Wicket - Multi Instance Support

Multiple browser windows viewing the same application? You can turn on multi-window support in your application init method by adding: getPageMapSettings().setAutomaticMultiwindowSupport(true) - I think that's the naming This uses different page maps for each window / tab that's open. --

Re: LDM with Generics for DropDownChoice

On Wed, 25 Feb 2009, Timo Rantalaiho wrote: I'd say that ListView is wrong here. I created a new Jira issue on fixing that https://issues.apache.org/jira/browse/WICKET-2126 and will do if there are no objections or better ideas. Well, Igor objected very convincingly :) So now there

[vote] In Wicket 1.4 and onwards, remove widening from the list of choices model in DropDownChoice, changing it from IModelList? extends Foo to IModelListFoo

Background: https://issues.apache.org/jira/browse/WICKET-1512 https://issues.apache.org/jira/browse/WICKET-2126 http://www.nabble.com/LDM-with-Generics-for-DropDownChoice-td22155211.html This works: = clips public static void

Re: [vote] In Wicket 1.4 and onwards, remove widening from the list of choices model in DropDownChoice, changing it from IModelList? extends Foo to IModelListFoo

[X] Yes, change the DropDownChoice constructor to take the choices list as IModelListT or ListT without the wildcard - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail:

Re: [vote] In Wicket 1.4 and onwards, remove widening from the list of choices model in DropDownChoice, changing it from IModelList? extends Foo to IModelListFoo

[X] Yes, change the DropDownChoice constructor to take the choices list as IModelListT or ListT without the wildcard [ ] No, keep DropDownChoice as it is in Wicket 1.4-rc2 Best regards, --- Jan. - To unsubscribe,

Re: [vote] In Wicket 1.4 and onwards, remove widening from the list of choices model in DropDownChoice, changing it from IModelList? extends Foo to IModelListFoo

[X] Yes, change the DropDownChoice constructor to take the choices list as IModelListT or ListT without the wildcard ** Martin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands,

Re: [vote] In Wicket 1.4 and onwards, remove widening from the list of choices model in DropDownChoice, changing it from IModelList? extends Foo to IModelListFoo

[X] Yes, change the DropDownChoice constructor to take the choices list as IModelListT or ListT without the wildcard Regards, Erik. -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ - To unsubscribe,

Re: GSoC ideas for 09

Having done Gsoc for 2008 (Unrelated OSS project) I'd suggest extremely well defined projects, extremely clear project management and quite a few introductions for tasks expected, not to mention multiple mentors (For picking up slack) defined targets and monitoring as if this was a VC set of