cool.
--- Arron Bates <[EMAIL PROTECTED]> wrote:
> > The 'nameList.value' is being used to lookup of
> the
> > messages/errors that were stored under this in the
> > ActionMessages. ActionMessages has an internal
> Map
> > and uses a key (normally the property name and
> there
> > is also GLOBAL
> The 'nameList.value' is being used to lookup of the
> messages/errors that were stored under this in the
> ActionMessages. ActionMessages has an internal Map
> and uses a key (normally the property name and there
> is also GLOBAL_MESSAGE constant) to store
> messages/errors associated with that
The 'nameList.value' is being used to lookup of the
messages/errors that were stored under this in the
ActionMessages. ActionMessages has an internal Map
and uses a key (normally the property name and there
is also GLOBAL_MESSAGE constant) to store
messages/errors associated with that field.
> I
That all seems cool, and if the test works, all the better :)
To confirm what's happening there...
It's fetching the "nameList.value" property off the same bean as the
text fields. To read the markup, the messages and errors would then be
calling on the same property. Internally the name is being
I'm not 100% I'm sure I'm following what the problem
is (probably missed some other e-mails). I was going
to talk to you Aaron when I went to do these, but it
seemed very simple so I went ahead and made them. I
just wanted the nested messages and errors tags to be
able to get the property name o
Just curious as to the applicability of the Errors an Messages tags in
the nested context...
Because the nested tags use the one bean reference, I'm finding it hard
to visualise using these tags within context. In the original tags,
everything was an island, so it was all fine, but nesting agains
