Hi,
you are right. slashes in resourceName are widely supported and widely used
(eg Webjars and Primefaces). It's a bug in the spec.
The relevant text is in the JSF 2.2 specification page 77, chapter 2.6.1.3
Resource Identifiers:
"The set of characters that are valid for use in the localePrefix,
libraryName, libraryVerison, *resourceName* and resourceVersion segments of
the resource identifier is specififed as XML NameChar *excluding the path
separator* and ‘:’ characters."
Best regards,
Arend
On Fri, Jan 27, 2017 at 9:20 PM, Thomas Andraschko <
andraschko.thomas_at_gmail.com> wrote:
> Hey,
>
> AFAIK a slash in the "name" works in both MyFaces and Mojarra and almost
> every component library uses it via @ResourceDependency.
> But not sure about the spec text in detail.
>
> Also using slash in the library works without configuration in Mojarra. In
> MyFaces you have to set: org.apache.myfaces.STRICT_JSF_
> 2_ALLOW_SLASH_LIBRARY_NAME.
>
> Regards,
> Thomas
>
> 2017-01-27 18:50 GMT+01:00 arjan tijms <arjan.tijms_at_gmail.com>:
>
>> Hi,
>>
>> Generally, every change, bug fix, typo, etc counts as a change against
>> the lock-down. Only very critical things in mostly new functionality that
>> would block a release can be done, but at the sole discretion of the spec
>> leads (Ed Burn and Manfred Riem).
>>
>> Hopefully though we can start a new spec cycle soon.
>>
>> Kind regards,
>> Arjan
>>
>>
>>
>> On Fri, Jan 27, 2017 at 6:23 PM, Arend v. Reinersdorff <arend_at_arendvr.com
>> > wrote:
>>
>>> Hi Arjan,
>>>
>>> not sure if it makes a difference with the lock-down: This is not about
>>> new functionality but about fixing a bug in the spec.
>>>
>>> As is the spec forbids resources like this (path separator in
>>> resourceName):
>>> <h:outputScript library="primefaces" name="jquery/jquery.js" />
>>>
>>> Best regards,
>>> Arend
>>>
>>>
>>> On Fri, Jan 27, 2017 at 2:42 PM, arjan tijms <arjan.tijms_at_gmail.com>
>>> wrote:
>>>
>>>> Hi Arend,
>>>>
>>>> Unfortunately JSF 2.3 is now in lock-down mode wrt spec/api changes, so
>>>> any new change will have to be diverted to JSF.next.
>>>>
>>>> Kind regards,
>>>> Arjan
>>>>
>>>>
>>>> On Thu, Jan 26, 2017 at 10:58 PM, Arend v. Reinersdorff <
>>>> arend_at_arendvr.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> could this issue be addressed in JSF 2.3? It has not been fixed in the
>>>>> public review draft. Path separators in resourceNames are widely used:
>>>>> https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1366
>>>>>
>>>>> Best regards,
>>>>> Arend
>>>>>
>>>>>
>>>>
>>>
>>
>