users@javaserverfaces-spec-public.java.net

[jsr344-experts mirror] [jsr344-experts] Re: [996-ConfigurableResourcesDirectory] PROPOSAL

From: Çağatay Çivici <cagatay.civici_at_gmail.com>
Date: Wed, 29 Feb 2012 23:47:36 +0200

> javax.faces.ClasspathResourcesDirectory
>
> If this param is set, it must not start with a "/" and the runtime will
> interpret its value to be the path of the resources directory for
> resources packaged in the classpath as specified in section 2.6. If not
> specified, the default value is "META-INF/resources".

META-INF/resources will always be scanned whether or not this context param is defined right?

> I like the idea. Obviously JSF is not the only EE technology to suffer from context-paramitis. Should we try to bring this up at the servlet level? Ed
+1, we already have faces-config.xml and bunch of settings in web.xml. Less xml, more attractive JSF is.

Regards,

On 29.Şub.2012, at 07:17, Ed Burns wrote:

> One more context param attribute, with addition to dozens of others...
> You recall me my old idea to put all configuration options into single class, where each option has its own getter, with appropriate validation and defaults.
> It should read all options from context parameters in default implementation, or can be replaced in faces config by custom class.
> RichFaces has such class, and I saw similar in Mijarra implementation. Why do not move it into public ?
> I like the idea. Obviously JSF is not the only EE technology to suffer from context-paramitis. Should we try to bring this up at the servlet level? Ed

Çağatay Çivici
Principal Consultant
PrimeFaces Lead | JSF EG Member

Prime Teknoloji
Bilkent Cyberpark, A-303d
06800 Ankara/Turkey
Tel: +90 312 265 05 07
http://www.prime.com.tr