[
https://issues.apache.org/jira/browse/ADFFACES-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated ADFFACES-315:
----------------------------------------
Fix Version/s: 1.0.0-incubating-core
Affects Version/s: 1.0.0-incubating-core
> Want API to disable dialog navigation outcome handling
> ------------------------------------------------------
>
> Key: ADFFACES-315
> URL: https://issues.apache.org/jira/browse/ADFFACES-315
> Project: MyFaces ADF-Faces
> Issue Type: New Feature
> Affects Versions: 1.0.0-incubating-core
> Reporter: Adam Winer
> Assigned To: Adam Winer
> Fix For: 1.0.0-incubating-core
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
