On 10/31/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
In particular, if you decide to implement this feature, consider packaging it inside a separate JAR file with its own embedded META-INF/faces- config.xml file that defines the custom navigation handler. That way, it is self configuring -- to use the feature, just drop the JAR into your app.
Craig
Hi!
> 1.) Seperate NavigationHandlerImpl
IMHO, this is a must! I think we should *not* implement stuff which
"silently" changes/enhances the behaviour - especially in myfaces-impl!!
The TCK might forbid this change anyway ...
> 2.) Configurable Option
not required, as everyone can configure this NH in faces-config.xml.
In particular, if you decide to implement this feature, consider packaging it inside a separate JAR file with its own embedded META-INF/faces- config.xml file that defines the custom navigation handler. That way, it is self configuring -- to use the feature, just drop the JAR into your app.
Craig
> 3.) Custom NH code in the wiki with a "discouraged" note
This might be a good compromise.
>
> 4.) Not at all
I do not mind ;-)
5) Add the new NH to the sandbox (but not configured by default)
I like it to put stuff to the sandbox first and see if the community is
willing to use them .... something like "the time will tell if its worth".
Ciao,
Mario
