> I'm curious though, how did you know about the FieldToTracker map and the
> control name?
Whenever it's not obvious what's happening I step into the code with a
debugger. Set a breakpoint before you call recordError and you can step through
the whole process. Then you can set a breakpoint in
Thanks again Josh. That was simple. I'm curious though, how did you know
about the FieldToTracker map and the control name? I gave a shot at
looking through the Tapestry source code to try and see if I could
figure something out by that, but I felt a bit lost and reading the
Errors class mislea
Sooo...
When you set an error on a field before it's been rendered then the
error goes into the list of errors (so you see it in t:errors) but the
connection between the field and the error is lost. The reason is that
the fieldToTracker map is keyed on the fields control name which isn't
allocated
On Wed, 18 Aug 2010 18:16:31 -0300, Rich M wrote:
Hi,
Hi!
Strangely enough, if I include in the form of CustomerLogin,
it actually displays the error, which really suprised me when I did a
sanity check. I'm not sure why that gets triggered and not the AJAX
bubbles from the ValidationD
Hi,
I'm still having a hard time grasping this. I tried thinking of a way to
trigger an event in the CustomerLogin component to resubmit so the
errors would show, no go. I tried using the onActivate of the container
Page to load things in the CustomerLogin component and then resubmit the
page
Hi,
a somewhat related question. It's now possible thanks to the Decorator
for my webapp to display validation bubbles after a form submit. I'd
also like to be able to set an error somewhere in the beginning of the
rendering process and have it show. I'm having a hard time figuring out
how to
Thanks Josh,
that was exactly what I was looking to do. Hopefully I'll be able to
start seeing these things on my own sometime soon!
-Rich
On 08/11/2010 08:11 PM, Josh Canfield wrote:
If you are looking to get the error bubble to pop up after you submit
the form you could use this:
public c
You can control the look of the errors component using CSS. I also use
a component that extends Errors so that it can render outside of the
form:
public class FormErrors extends Errors {
@Parameter(required = true)
private Form _form;
@Inject
private Environment _environment;
Hi,
I've found resources that explain how to remove the validation bubbles,
but I'm looking to display validation bubbles similar to how it's
possible to record form errors to after a 'failed' form
submission.
I have tight spacing in the UI layout and having to accommodate for the
isn't m
