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. :)
Mike Kienenberger wrote:
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 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 the simple example pages, then
the warning goes away.
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Mike Kienenberger wrote:
> 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
> (i.e. not by a JSP tag) you should assign it an explicit static id or
> assign it the id you get from the createUniqueId from the current
> UIViewRoot component right after creation!
>
> clientID = parent.getClientId(getFacesContext());
>
> parent= UIViewRoot (id=44)
> _attributesMap= null
> _childrenList= _ComponentChildrenList (id=100)
> _clientId= "_id0"
> _events= null
> _facesListeners= null
> _facetMap= null
> _id= "_id0"
> _locale= Locale (id=106)
> _parent= null
> _rendered= null
> _rendererType= null
> _renderKitId= "HTML_BASIC"
> _transient= false
> _uniqueIdCounter= 1
> _valueBindingMap= null
> _viewId= "/masterDetail.jsp"
>
>
>
