What scares me about this is that it *appears* to work just fine when
putting a DataContext in a Tapestry Visit object.
Tapestry promises to run all Page objects on a single thread, but what
is far from obvious is that access to the Visit object is not
similarly single threaded.
Is it (in theory) possible for a DataContext to throw an exception if
misused in this way?
-- Øyvind Harboe http://www.zylin.com
This archive was generated by hypermail 2.0.0 : Thu Oct 12 2006 - 03:41:17 EDT