Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

On Mon, 17 Nov 2014 19:59:52 -0200, D Tim Cummings wrote: Thanks Charlouze. This sums up the problem nicely. I have added your comment to https://issues.apache.org/jira/browse/TAP5-2204 which was supposed to resolve this issue but hasn’t.

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

I ran into this problem this morning too. I did my investigation in order to post a mail later but I found yours first. 2014-11-17 22:59 GMT+01:00 D Tim Cummings : > Thanks Charlouze. This sums up the problem nicely. I have added your > comment to https://issues.apache.org/jira/browse/TAP5-2204 <

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

Thanks Charlouze. This sums up the problem nicely. I have added your comment to https://issues.apache.org/jira/browse/TAP5-2204 which was supposed to resolve this issue but hasn’t. Someone needs to reopen this jira issue. Tim > On 18 Nov 2014

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

> On 18 Nov 2014, at 02:44, Thiago H de Paula Figueiredo > wrote: > > On Mon, 17 Nov 2014 10:41:20 -0200, D Tim Cummings > wrote: > >> Thanks. That wasn’t my question but it does help me. With secure="always", I >> would need the model for render and form submission. So according to what >

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

I agree with Tim. Documentation says that the default is auto and does not require the model to be set in order to pass the submission process. I think it's a bug. As you can see in the select component code

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

On Mon, 17 Nov 2014 10:41:20 -0200, D Tim Cummings wrote: Thanks. That wasn’t my question but it does help me. With secure="always", I would need the model for render and form submission. So according to what you are saying I could init the model in onActivate() OR onPrepare() OR (onPrep

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

Thanks. That wasn’t my question but it does help me. With secure="always", I would need the model for render and form submission. So according to what you are saying I could init the model in onActivate() OR onPrepare() OR (onPrepareForSubmit() AND setupRender()). My actual question is why do I

Re: 5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

If you init your model in setupRender it will be null upon form submit (as it is not a render request) - You can use onActivate, onPrepareForSubmit or onPrepare to init the model prior to form submission. -- Chris On Mon, Nov 17, 2014 at 12:39 PM, D Tim Cummings wrote: > I am trying to underst

5.4 beta 22 - Select component secure="auto" throws exception: model is bound to null.

I am trying to understand the new attribute "secure" of the "select" component. This is either a bug or I don’t understand the attribute. I am running Tapestry 5.4 beta 22. I have copied the code from the Jumpstart7 AJAX filtered grid example where firstInitials is a List created in the setupR