I think the secure parameter should default to a symbol. And the default
for the symbol should be false
I completely agree with you Bob, it broke my code and left me going in
circles trying to figure out why all of a sudden I was getting these select
exceptions when I was implementing the component no differently than I have
have.
On Wed, Oct 16, 2013 at 2:03 PM, Bob Harner wrote:
> The work-arou
The work-around of setting the secure parameter to "false" works for me (if
I do it on *all* the selects in the form).
The issue was caused by the fix for TAP5-2179 ("The Select component can be
hacked to select a value not in the SelectModel").
I agree with Lance that the secure parameter's defa
It's still failing with secure="false", the only way to get it to work is
to @Persist SelectModel computerModels.
btw, the onValueChanged method in my above example should be
onValueChangedFromComputer.
On Wed, Oct 16, 2013 at 9:38 AM, Lance Java wrote:
> It seems like a new 'secure' parameter
filed jira issue
https://issues.apache.org/jira/browse/TAP5-2204
On Wed, Oct 16, 2013 at 10:03 AM, George Christman
wrote:
> It's still failing with secure="false", the only way to get it to work is
> to @Persist SelectModel computerModels.
>
> btw, the onValueChanged method in my above example
It seems like a new 'secure' parameter has been added to select which
defaults to true (value must exist in the model).
Try setting secure="false"
I think this should be the default to maintain backwards compatibility.
Sample code and full stack. I'm at my day job and unable to recreate my
actual data model, so please keep in mind I use a multi tier selection
model, ie Category, Year, Make, Model, Trim. This worked without issue
prior to 5.4.21. The selectModel data is dependent upon the select model
value, so I'
Can you post a stack trace?
You can either persist your SelectModel, or recreate it in your
onPrepareForSubmit method (or in onPrepare, which gets called both for form
render and submit.
Yes, please create a JIRA issue.
On Oct 16, 2013 8:34 AM, "George Christman" wrote:
> Thanks Bob for correcting the subject line to 5.4,
Thanks Bob for correcting the subject line to 5.4, I forget T4 actually
existed.
Unless there is another work around, I was unable to get this to work
without the use of @Persist. Hopefully this is just a regression bug that
can be resolved. Should this be reported?
On Wed, Oct 16, 2013 at 7:01
I noticed a couple of days ago in 5.4 alpha 22 that the SelectModel is now
being used on form render AND submission whereas it used to be used only on
render of the form. This is a big deal performance-wise because creation of
the SelectModel commonly involves a database query to populated a list o
11 matches
Mail list logo
