Paul,
Not sure I agree that the approach violates the spec, given it would be
'off' by default (it seems similar to Trinidad's existing customization of
the 'client' state saving setting), but I do see your point on
documentation. For sure your approach could also work. I'll take a look at
this
Guys,
I don't think it's possible to dynamically specify wildcard config loading
patterns for JSF currently. However, most all other frameworks today seem
to be able to handle something similar for loading files by naming/location
conventions. I know JSF will pick-up META-INF/faces-confg.xml
Hi Danny,
yes!!!
regards,
Martin
On Mon, Feb 25, 2008 at 10:56 AM, Danny Robinson
[EMAIL PROTECTED] wrote:
Guys,
I don't think it's possible to dynamically specify wildcard config loading
patterns for JSF currently. However, most all other frameworks today seem
to be able to handle
Sounds like a good idea to me too.
On Mon, 2008-02-25 at 18:29 +0100, Martin Marinschek wrote:
Hi Danny,
yes!!!
regards,
Martin
On Mon, Feb 25, 2008 at 10:56 AM, Danny Robinson
[EMAIL PROTECTED] wrote:
Guys,
I don't think it's possible to dynamically specify wildcard config
Danny,
Sounds like a good idea. I am not sure if the non-spec compliant use of
the parameter javax.faces.CONFIG_FILES in conjunction with a parameter
not defined by the spec, like
org.apache.myfaces.ENABLE_WILD_CARD_IN_CONFIG_FILES,
would violate the spec. At the very least it would
