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 of objects.
I haven't yet spent the time to look at this closely to see if I am doing something wrong, but it looks like a regression to me. On Oct 15, 2013 11:33 PM, "George Christman" <gchrist...@cardaddy.com> wrote: > Some additional information, this appears to last work correctly in version > 5.4-alpha-20, but becomes broken in 5.4-alpha-21 - current. > > > On Tue, Oct 15, 2013 at 11:09 PM, George Christman > <gchrist...@cardaddy.com>wrote: > > > Hello, I have a year, make, model select menu in my application. I set > the > > model of the current menu based on the previous select menu using the > > onValueChanged event and ajax zone component. The select menu in T.4.22 > > appears to be calling the SelectModel before it calls the onValueChanged > > event resulting in the following exception. > > > > org.apache.tapestry5.ioc.internal.util.TapestryException > > > > *Parameter 'model' of component Test:carmake is bound to null. This > > parameter is not allowed to be null.* > > locationclasspath:org/company/tapdemo/pages/Test.tml, line 9 > > > > I used Geoff's example from jumpstart found below as a test to find the > > same issue still existed in 4.22. I tried the example in 3.7 and didn't > > experience any issues. Should I file a bug? > > > > > http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/selectmore1 > > > > > > > > -- > > George Christman > > www.CarDaddy.com > > P.O. Box 735 > > Johnstown, New York > > > > > > > -- > George Christman > www.CarDaddy.com > P.O. Box 735 > Johnstown, New York >
