It depends. This is true for resources accessed via EL #{resource} (which I do
not recommend btw because it's a HUGE performance hog - better use restful
resources [1]). For facelets this only got fixed in JSF-2.2. In JSF-2.0 and 2.1
you still need the ResourceResolver to load facelets from a jar [2].
LieGrue,
strub
[1]
http://www.jakobk.com/2011/11/bachelor-thesis-about-relative-resource-handler/
[2]
http://stackoverflow.com/questions/6199458/how-to-create-a-modular-jsf-2-0-application/6201044#6201044
On Friday, 28 February 2014, 8:39, Martin Hoeller <mar...@xss.co.at> wrote:
On 27 Feb 2014, Mark Struberg wrote:
>
>> JSF by default loads the resources from the local WAR classpath only. But
>> you can easily write your own ResourceResolver which picks the stuff from
>> the ClassPath as well.
>>
>> An example can be found here:
>> http://ocpsoft.org/opensource/create-common-facelets-jar/
>> See CustomResourceResolver.
>
>Very big on the linked site is stated "In JSF2, this process is no longer
>required.". An we are talking about JSF2 here.
>
>Beside this, (as far as I understood it) the ResourceResolver is just
>responsible for resolving resources like images, CSS and the like at
>application runtime. We are talking about registering component,
>converters, etc. at application startup time here and I don't think the
>ResourceResolver could be any help in this case.
>
>thx anyway,
>
>- martin
>
>
