The fields are null because the values are often stored elsewhere; this is part of the logic that allows a single page instance to be actively shared across threads.
Its much more likely that your application is at fault. For example, that "cursor" parameter may be bound to a property that is non-null when the page renders, but is then null when the associated link is clicked. The field that the parameter is ultimately bound to should be persisted in the session, or on the client (using either page activation context, or the event's context). On Thu, Nov 1, 2012 at 9:52 PM, Ken in Nashua <kcola...@live.com> wrote: > > Just another byproduct of things that occur and run amuck within the app at > runtime > > An unexpected application exception has occurred.Parameter 'cursor' of > component Home:gallerywidget is bound to null. This parameter is not allowed > to be null. > > > > I guess I need to review all the code and see whats taking this down and > start pulling it apart to try ans flush it out. > not a fun bug... but I will be happy to find it > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
