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 against the one bean makes it a little fuzzy. Referencing the different bean means implanting a new root tag, which would mean you'd have to nest the tags all over again to get to the same point. It would be easier to go the route of the original errors/messages tags. I realise that it'd be really handy to be able to get at the same property that a text box is working off of, but the separate bean issue meant that I basically put it down to being out of context and as a result I didn't include them in the tags when I first wrote them. One way I can see it working is to make a small departure from the way the rest of the nested tags work, and allow the referencing of a different bean. This then raises the problem that if you do it for one, you should possibly allow the others. Not impossible. Just a check in the tags to see if there's a supplied bean name reference, if there is, allow it to go through. Up to this point I kept it as a "best practice" to leave the naming of any bean up to the root tag (well, it enforced it really). Means that the requirement of the root tag should probably be loosened up if a bean is explicitly provided. There will possibly be an ambiguity as to how far back the property will be calculated, and the definition of the nested tags being "properly marked up". But I'm probably over-thinking the issue. Any other thoughts?... any other committers actually using the nested tags?... :) Arron. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
