You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Gary VanMatre (JIRA)" <ad...@incubator.apache.org> on 2006/12/04 20:21:22 UTC

[jira] Commented: (ADFFACES-315) Want API to disable dialog navigation outcome handling

    [ http://issues.apache.org/jira/browse/ADFFACES-315?page=comments#action_12455411 ] 
            
Gary VanMatre commented on ADFFACES-315:
----------------------------------------

An annotation library would be interesting.   

Something like:
    @InternalView(viewId="/myview")
         or 
    @InternalNavigationHandler(priority=1);

The shale tiger library does this kind of thing for managed beans, components, listeners and converters.  It uses a context listener on startup to scan and process annotations.

http://svn.apache.org/viewvc/shale/framework/trunk/shale-tiger/src/main/java/org/apache/shale/tiger/view/faces/LifecycleListener2.java?view=markup

Since Trinidad requires SE 1.5, it would seem a natural fit.

> Want API to disable dialog navigation outcome handling
> ------------------------------------------------------
>
>                 Key: ADFFACES-315
>                 URL: http://issues.apache.org/jira/browse/ADFFACES-315
>             Project: MyFaces ADF-Faces
>          Issue Type: New Feature
>            Reporter: Adam Winer
>         Assigned To: Adam Winer
>
> We need to build a custom navigation handler using Trinidad.  We want to support "dialog:" navigational outcomes, but because of the design of this navigation handler, the order of processing is critical:  if this navhandler wraps the Trinidad navhandler, things work, but if the opposite order happens, everything breaks.
> Because, there's no way in JSF 1.2 or 1.1 to force an ordering of delegation, we either have to support a custom method of setting up an extra nav handler (as per the custom view handler hook), or support disabling the nav handler altogether so its code can be duplicated.  Since the nav handler is very simple code that just calls other public APIs, the latter is preferable.  Ideally, this will be zero-config.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira