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
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 to lend a helping hand to understand it.
Thanks
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Can someone explain the error below?
The page is loading correctly, but when I hit the search button I get this
error.
the onPrepare is the last method, after that I get the exception.
java.util.NoSuchElementException
# java.util.AbstractList$Itr.next(Unknown Source)
#
org.apache.tapestry5.core
actions, in which case a NoSuchElementException should not occur) or
that a better exception message could be produced indicating that the
number of items in the loop does not match the count expected by the
stored actions.
Kind regards,
Joachim
Joachim Van der Auwera wrote:
Sorry, this time with
Sorry, this time with stacktrace...
I have a form which causes the following exception on submit.
This seems to be a problem with the advance_volatile commands in the form.
I am using tapestry 5.0.18. Any ideas how to fix this?
Stack trace below,
Thanks for the help.
Joachim
2009-01-13 18:31:
I have a form which causes the following exception on submit.
This seems to be a problem with the advance_volatile commands in the form.
I am using tapestry 5.0.18. Any ideas how to fix this?
Stack trace below,
Thanks for the help.
Joachim
--
Joachim Van der Auwera
PROGS bvba, progs.be
