Mike,
I get that warning message if I use a h:form with no id attribute.
In fact, I see this warning on almost every page in the simple
Tomahawk example app (and they don't have an id set on the form).
Perhaps the warning message could be more clear?
To put it another way, if I add an id to
Jeff,
Mind opening an issue on this? I don't remember if h:form requires an
id, but I don't think it is supposed to.
On 3/30/07, Jeff Bischoff [EMAIL PROTECTED] wrote:
Mike,
I get that warning message if I use a h:form with no id attribute.
In fact, I see this warning on almost every page
According the the Sun docs [1], it is not a required attribute. Is that
official enough? (There is nothing in the spec itself about attributes
of core tags, is there?)
So should we remove this warning altogether, or just change it? I would
be happy to open the JIRA for it, after lunch. :)
Upon further testing, my initial response may have been misleading. Back
when I had JSP in my application, assigning explicit form ids is what
got rid of this warning message.
However in further testing today with the tomahawk examples from the
release candidate files, I found this is no
I'm not going to try to track this one down since I don't do jsp.
But here's a strange warning -- UIViewRoot got assigned an automatic
id in masterDetail.jsf.
INFO: WARNING: Component _id0 just got an automatic id, because there
was no id assigned yet. If this component was created dynamically
