Thanks Geoff...
I added clientValidation=false on my form definition and that caused it to stop
before I even asked about this..
...
I was alarmed it happened on my live site.
So I am a bit stale on what can happen to live sites.
Not sure what could be going on under the hood... but I
It sounds like this might be helpful:
http://tapestry.apache.org/overriding-exception-reporting.html
On Sat, Mar 23, 2013 at 9:34 AM, Ken in Nashua wrote:
> I guess I am wondering if i can catch these exceptions in a centralized
> place and just present the most meaningful text in a popup dialo
I guess I am wondering if i can catch these exceptions in a centralized place
and just present the most meaningful text in a popup dialog for the user to
acknowledge and keep the page user interface intact.
The JIRA is interesting and I agree it does seem like a lot of
plumbing to do this. I suspect this could also be solved with an
@CompositeField annotation and a worker. Your example is similar to
what I came up with except I need to do validation so I have to create
a Runable.
private static class
OK that makes more sense. It's basically the same as using the request
object. If we don't hear anything this weekend I'll post over on the
dev list on Monday. Perhaps we can get an explanation about how
Bindings and Parameters really work. I think I understand why the code
I have works but I might
Ah, sorry, I see where you are coming from. Tapestry has a special type of
thread local which is cleaned up after each request. It's called a
PerThreadValue. That's what I was ultimately referring to.
On 23 Mar 2013 01:30, "Barry Books" wrote:
> My impression was Thread Local gives you an instanc
