Hi,
Am 03.03.2013 um 17:25 schrieb Leonardo Uribe <lu4242_at_gmail.com>:
> It is possible we have a problem in the default TagDecorator, because in
> that part it is assumed that "jsf" prefix is associated to the namespace,
> no matter how it was defined on the page.
the default TagDecorator definitely checks the namespace URI (it simply calls javax.faces.view.facelets.TagAttributes#get(String ns, String localName)).
>
> In the javadoc of TagDecorator it says this:
>
> "... A selector attribute name prefixed with jsf: means the tag is treated
> as if it were in the http://xmlns.jcp.org/jsf namespace. …"
This sentence is related to the mapping table above it. The table uses "jsf:" as a shorthand for the
http://java.sun.com/jsf namespace. Maybe we should simply reduce this sentence to: "A selector attribute name prefixed with jsf: means the attribute is in the
http://xmlns.jcp.org/jsf namespace"
But I think, a native english speaker should disambiguate this sentence.
>> Andy Schwartz <andy.schwartz_at_oracle.com> hat am 3. März 2013 um 14:05
>> geschrieben:
>>>
>>> I haven't had a chance to read up on the context for this, but I wanted
>>> to chime in to say that the JSF spec should never associate behavior
>>> with namespace prefixes. The spec should only associate behavior with
>>> namepsaces. Sure, the spec can recommend conventions for namespace
>>> prefix mappings. However, our users should always be free to define
>>> their own mappings.
>>>
>>> If we have cases in the spec where we require that a namespace prefix
>>> has some meaning regardless of how that prefix is mapped, we need to fix
>>> this.
Absolutely. And I'm pretty sure, we don't do it.
Ciao Frank