[jsr-314-open] [OT] faces-config.xml names

[Andy Schwartz]

Gang -

Just wanted to send out one more ping on this before we pick our names 
for Trinidad/ADF Faces.

It seems clear that the current restrictions on faces-config.xml names 
was not intentional.  Is there any hope of getting some solution in 
place quickly, eg. could we:

- Doc this as a spec errata for the next MR
- Tweak Mojarra/MyFaces to allow NMTOKENs for names

This seems like it should be fairly trivial to do, but I have no idea 
whether there are some process barriers that would prevent us from doing 
this.

Ed/Roger -

Any thoughts on whether this might be possible?  (If not, I'll 
understand, but would be good to know either way.)

Andy

Andy Schwartz wrote:
> Thanks Dan.
>
> BTW, regarding:
>
>> The desired semantics are to match the XML NMTOKEN type:
>
> Looking back at our original email thread, there was discussion of 
> using the XML ID type (which also allows '.').  It seems fairly clear 
> that the choice of javaee:java-identifierType did not match our intent.
>
> Ed, Roger -
>
> Can we find some way to address this, at the spec and/or 
> implementation level?  Ideally we want to do this before too many more 
> frameworks publish their faces-config names.
>
> Andy
>
> Dan Allen wrote:
>> \p in the regexp basically the dot matcher (.) for specific unicode 
>> classifications. So the regex says roughly:
>>
>> starts with a letter, _ or $
>> can have any number of letters, _ or $
>>
>> Letter is a loose term that encompasses strange symbols you will 
>> likely never type (at least not if you are writing in English, but we 
>> are friendly to other character sets as well where the dot character 
>> would not match).
>>
>> Still, no literal dot (.) allowed.
>>
>> -Dan
>>
>> p.s. Not sure why we select the $ to be allowed. Or is that the end 
>> of line matcher? If so, I still don't get what it is trying to say.
>>
>> On Tue, Oct 20, 2009 at 2:48 PM, Andy Schwartz 
>> <andy.schwartz at oracle.com <mailto:andy.schwartz at oracle.com>> wrote:
>>
>>     Gang -
>>
>>     The spec defines the name element as:
>>
>>                    <xsd:element name="name"
>>                                 type="javaee:java-identifierType"
>>                                 minOccurs="0"
>>                                 maxOccurs="1">
>>
>>
>>     javaee:java-identifierType is:
>>
>>         <xsd:complexType name="java-identifierType">
>>            <xsd:annotation>
>>              <xsd:documentation>
>>
>>            The java-identifierType defines a Java identifier.
>>            The users of this type should further verify that
>>            the content does not contain Java reserved keywords.
>>
>>              </xsd:documentation>
>>            </xsd:annotation>
>>            <xsd:simpleContent>
>>              <xsd:restriction base="j2ee:string">
>>            <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
>>              </xsd:restriction>
>>            </xsd:simpleContent>
>>          </xsd:complexType>
>>
>>
>>
>>     My regular expression parsing skills are not what they should be,
>>     but I believe that this is unintentionally overly strict.  The
>>     desired semantics are to match the XML NMTOKEN type:
>>
>>     http://www.w3.org/TR/2000/WD-xml-2e-20000814.html#NT-Nmtoken
>>
>>     Which allows '.' (and other characters too, like '-', ':').
>>
>>     This is going to require a loosening of the spec - in particular,
>>     in the XSD for faces-config.xml.  Can we find some way to address
>>     this?  Perhaps as a spec errata that allows implementations to
>>     accept qualified ids?
>>
>>     Andy
>>
>>     lincolnbaxter at gmail.com <mailto:lincolnbaxter at gmail.com> wrote:
>>
>>         Agreed. I don't know if that's something we can fix? Should be
>>         fixed IMO. Though I don't understand the reasons it wasn't
>>         included at all, so I can't really theorize.
>>
>>         Sent from my Verizon Wireless BlackBerry
>>
>>         
>> ------------------------------------------------------------------------
>>         *From: * Dan Allen <dan.j.allen at gmail.com
>>         <mailto:dan.j.allen at gmail.com>>
>>         *Date: *Tue, 20 Oct 2009 14:20:53 -0400
>>         *To: *<lincolnbaxter at gmail.com
>>         <mailto:lincolnbaxter at gmail.com>>; <jsr-314-open at jcp.org
>>         <mailto:jsr-314-open at jcp.org>>
>>         *Subject: *Re: [jsr-314-open] [OT] faces-config.xml names
>>
>>
>>
>>         On Tue, Oct 20, 2009 at 2:16 PM, <lincolnbaxter at gmail.com
>>         <mailto:lincolnbaxter at gmail.com>
>>         <mailto:lincolnbaxter at gmail.com
>>         <mailto:lincolnbaxter at gmail.com>>> wrote:
>>
>>            Andy,
>>
>>            Prettyfaces uses ocpsoft_pretty_faces (dot is not an allowed
>>            character and will cause deploy failure)
>>
>>
>>         Too bad. I would have voted for the Java namespace style. I
>>         like org.apache.myfaces.trinidad and org.ocpsoft.prettyfaces
>>
>>         Either way, I would use a name that maps closely to the root
>>         package of the component library.
>>
>>         -Dan
>>
>>
>>         --         Dan Allen
>>         Senior Software Engineer, Red Hat | Author of Seam in Action
>>         Registered Linux User #231597
>>
>>         http://mojavelinux.com
>>         http://mojavelinux.com/seaminaction
>>         http://www.google.com/profiles/dan.j.allen
>>
>>
>>
>>
>>
>> -- 
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://www.google.com/profiles/dan.j.allen
>
>