So I ended up figuring out the issue.
My loop was nested within a zone, when the loop was loaded.
!request.xhr was blocking a query causing the result size to differ
between load and submit. On submit I was submitting values that the
onPrepare method wasn't aware of.
On Sun, Jan 25, 2015 at 6:18
Below is the tml code
12
13
14
15
16
17
18
19
20
21
22
java
@Property
private FacetView facetView;
@Property
private List> facetViews;
public void onPrepareFromFilterForm(String filterType) throws IOException {
try {
searchResponse = vehicleSearchD
Can you paste the source of FacetFilter.tml, and identify line 16, too?
On 25 Jan 2015, at 5:24 am, George Christman wrote:
> Hi guys, I've been seeing this exception a lot lately and I can't seem
> to track it down, I'm wondering if anybody has see anything like this
> before and might be able
Problem solved.
It seems that for some reason not entirely clear to me, there was a
difference in server side and client side state. The end result is the
exception below. I believe that either there is a mistake in the
comments in the code (about everything being driven by the stored
actions
