Dave.Sanders
3 Aug 2009, 7:01 AM
I tripped across this today and had to set breakpoints deep in DirectProxy to believe it. I'm sorry that I don't have a ready made case to post up for comment, but here's the scenario.
Two DirectStores on the same page. One store belongs to a grid, the other to a combo. The grid store passes a parameter via the load:
myStore.load({params:{myvar:'test'}});
My combo store does NOT use any parameters - its a simple data fetch:
myOtherStore.load();
In firebug I can see both of these come back with valid data every time, the first grid will load, but the second store never loads. If I debug it, the store is never filling with data, even though data is coming back and I've triple checked my store set up with field names and root matching perfectly.
If I change the second store to add a fake param, the data loads into the second store just fine, and is available in the combo. I traced this down to DirectProxy.js and found that the callback created in createCallback is never called after the request when no params are specified, so onRead is never called, and the data is never loaded.
Can someone else confirm this? Is this expected behavior or is this a bona fide bug? Its definitely NOT what I expected to happen.
Thanks
Dave
Two DirectStores on the same page. One store belongs to a grid, the other to a combo. The grid store passes a parameter via the load:
myStore.load({params:{myvar:'test'}});
My combo store does NOT use any parameters - its a simple data fetch:
myOtherStore.load();
In firebug I can see both of these come back with valid data every time, the first grid will load, but the second store never loads. If I debug it, the store is never filling with data, even though data is coming back and I've triple checked my store set up with field names and root matching perfectly.
If I change the second store to add a fake param, the data loads into the second store just fine, and is available in the combo. I traced this down to DirectProxy.js and found that the callback created in createCallback is never called after the request when no params are specified, so onRead is never called, and the data is never loaded.
Can someone else confirm this? Is this expected behavior or is this a bona fide bug? Its definitely NOT what I expected to happen.
Thanks
Dave