Hello all, One of my components has a problem with state. The component, a TreeList, implements PageDetachListener to reset it's state. The parent page also resets its state in its own detach method. However, when two requests come in simultaneously (or close to it), the second one always ends up with an exception: a particular data member is null.
It seems like the first request is modifying the component (resetting it) while the second one is still running through a Foreach loop on the same component (that is where the error occurs). This doesn't seem like the proper behavior. It's rather complicated, but I wondered if anyone had any pointers. There is only one page in the pool when the exception occurs (which means the requests weren't exactly at the same time), and I assume only one component then as well. But the two request seem to keep bumping into each other... I seem to remember there was some way to turn off the pooling to test this sort of thing, but I forgot the actual method. Any pointers appreciated, thanks. -Jason BTW - I'm still using Tapestry 2.0. I seriously hope I don't have to go through the upgrade process at this point... ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
