Re: Properties of model are set to NULL even though we have setRequired set to true

2010-04-06 Thread Wayne Pope
Hi, has anyone got any idea about this? I'm still 'spinning my wheels' on it. thanks for any help. On Fri, Apr 2, 2010 at 5:00 PM, Wayne Pope waynemailingli...@googlemail.com wrote: Hi, we've got several examples in our logs of properties of the model being set to null even though the

Re: Properties of model are set to NULL even though we have setRequired set to true

2010-04-06 Thread nino martinez wael
Hi Wayne I guess you've tried debugging it, so it's not a consistent error? Are you using any special web container or is wrapped somehow (like terracotta)? 2010/4/6 Wayne Pope waynemailingli...@googlemail.com: Hi, has anyone got any idea about this? I'm still 'spinning my wheels' on it.

Re: Properties of model are set to NULL even though we have setRequired set to true

2010-04-06 Thread David Chang
Hello Wayne, I understand your frustration. Recently, I got a similar case but it eventually turned out that it was my fault due to being new in Wicket. Long story short, for a dropdownchoice list with loadabledetachablemodel, I set up a load method, but in another place, I used

Re: Properties of model are set to NULL even though we have setRequired set to true

2010-04-06 Thread Wayne Pope
Hi Nino, we cannot reproduce it locally at all. Only happens in production. we have a straight forward setup - apache balancing to 2 tomcat instances - no clustering. really annoying! On Tue, Apr 6, 2010 at 3:51 PM, nino martinez wael nino.martinez.w...@gmail.com wrote: Hi Wayne I guess

Re: Properties of model are set to NULL even though we have setRequired set to true

2010-04-06 Thread Wayne Pope
Hi David, thing is - we cannot reproduce it at all, so we cannot debug at all and hence we don't know where to start. I suppose we could put debugging traces in our code and the wicket code to help us understand but that doesn't feel right.. On Tue, Apr 6, 2010 at 3:58 PM, David Chang

Properties of model are set to NULL even though we have setRequired set to true

2010-04-02 Thread Wayne Pope
Hi, we've got several examples in our logs of properties of the model being set to null even though the textfield is set to required. I have NO idea how on earth this can happen - its just doesn't make sense - and its really frustrating me!! here's an example: Caused by: