I agree with Gerald on using an attribute instead of a separate component - "forceSpan" should be just enough.
regards, Martin On 2/9/06, Gerald Müllan <[EMAIL PROTECTED]> wrote: > Hi Travis, > > > Not sure what you mean here? > > Currently there is one message tag for each input ajax field. This can > be reduced now to one messages tag for all the input ajax fields on > the site. > > So, if there are three input fields, you can define for example one > div element (with nice style), embedded the messages tag. Each time an > error occurs in one of the ajax fields, the error message is displayed > in this area. > > If you do not correct the errors in, all the fields, three messages > are shown there. > > However, it is also possible to have a message tag for each field, and > additional the messages stuff. Ok, this usecase maybe not really > useful :) > > > This is exactly what happens now, the span will be rendered no matter what, > > but you must use the s:message tag (which is the new HtmlMessageTag you are > > referring to) because it sets the id on the span. It sets the id so that > > the client side javascript knows what span to show the error message in. > > The examples in inputAjax.jsp show this error handling in action. > > Sure, you are right. But if we add a new attribute to the t:message > and t:messages components, which do exactly these things, there is no > need for an additional tag and an additional renderer. > > > The javascript definitely needs to be cleaned up, most of it could be put > > into a an external js file. I have been meaning to do that (i have a todo > > in the code somewhere about that), but this Maven thing has put a dent in my > > plans... ;) > > It seems you are really overhelmed with work, so I will do this issue for you > :) > > > The javascript needs to be somewhere, if not on the ajax end, then it has to > > be on the component end. It seems to me it should stay on the ajax side of > > things, so the message tag remains a simple dumb component that isn't tied > > to ajax. > > I agree. Ajax stuff should be not tied to the messag tag. > > > The new tag is required as I explained above because it needs to set the id. > > Yes, definitely required. But maybe added to t:message and t:messages. > See above. > > Seems that we really have a great component out there :) > > regards, > > Gerald > > -- > Gerald Muellan > Schelleingasse 2/11 > 1040 Vienna, Austria > 0043 699 11772506 > [EMAIL PROTECTED] > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
