On Wed, 23 May 2012 20:01:46 -0300, Sean sean.whet...@sirsidynix.com
wrote:
Thanks for the quick reply.
I changed selected to initialize in setupRender, and now I'm getting the
following exception.
Howard has been working on improvements to Tapestry internals under high
loads, so please
Thiago H de Paula Figueiredo wrote
On Wed, 23 May 2012 20:01:46 -0300, Sean lt;sean.whetten@gt;
wrote:
com.mycompany.product.module.components.search.account.CheckoutsList.setCurrentCheckout(CheckoutsList.java:170)
What's the code in this method?
You can find the code for that
On Wed, May 23, 2012 at 2:28 PM, Sean sean.whet...@sirsidynix.com wrote:
I recently upgraded to tapestry 5.3.3 from 5.0.1.x, and while running some
load tests using jmeter, I saw some new ConcurrentModificationException
errors. The test is simple, it just selects the first checkbox on the form,
Thanks for the quick reply.
I changed selected to initialize in setupRender, and now I'm getting the
following exception.
What's wierd about this one is that if I set a breakpoint in the
setCurrentCheckout method, it reports that selected and item are both
non-null and I can add strings to
