Andy Maag <andy.maag <at> gmail.com> writes: > The simplest manifestation of this problem is with the ServiceLink > component. Occasionally, we will see an error such as the one at the > bottom of this email. From my perusal of the Tapestry 3.0.3 source > code, this condition could only be reached if "null" were passed in as > the "service" parameter to the ServiceLink component. However, every > one of our ServiceLink instances uses one of the Tapestry constants > (i.e. <at> org.apache.tapestry.Tapestry <at> RESTART_SERVICE) for the service > parameter. > > Have others seen issues with parameters not being connected properly? > We had seen one or two cases in our application code that were fixed > by changing the parameter to "auto".
I'd guess that this is caused by concurrent accesses to the same page instance. After the component is rendered, its parameters are reset to their default value (null in most cases). If they're now accessed, they'll return null. To verify, try overriding prepareForRender() and cleanupAfterRender() to perform some logging. However, in theory, each thread should get its own page instance, so this could never happen. -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
