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 "Jim Dolinski (JIRA)" <ad...@incubator.apache.org> on 2007/04/20 18:55:15 UTC

[jira] Created: (ADFFACES-465)
<tr:commandNavigationItem
-------------------------

                 Key: ADFFACES-465
                 URL: https://issues.apache.org/jira/browse/ADFFACES-465
             Project: MyFaces ADF-Faces
          Issue Type: Bug
          Components: Components
    Affects Versions: 1.0.0-incubating-core
         Environment: Windows XP, Using Exadel IDE
            Reporter: Jim Dolinski


I have a issue when using the <tr:commandNavigationItem>.

I have a application that uses the <tr:page> tag. Inside of the tag, I am using the nodestamp facet with a commandNavigationItem. 

<f:facet name="nodeStamp">
	<tr:commandNavigationItem text="#{foo.label}"  
					          action="#{foo.getOutcome}"
			                  icon="#{foo.ico}"
			                  rendered="#{foo.shown}"
			                  disabled="#{foo.readOnly}"
                                          destination=""/>                                  
</f:facet>                      


The application is using a menu model to render the menu system. I have two "global" commandNavigationItems that are rendered, "help" and "login". I would like the help to use a external URI (destination) for the help file. All other navigation items will use a action for navigation. When I include the destination property on the component, it will disable any actions from firing (even if it is empty). Is there a way to mix the destination and action properties for "page" navigation? I tried including two commandNavigationItems within the nodestamp facet with no luck. Maybe there is a work around?

Thanks and Keep up the good work, Jim Dolinski

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (ADFFACES-465) Posted by "Jim Dolinski (JIRA)" <ad...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/ADFFACES-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Dolinski closed ADFFACES-465.
---------------------------------

    Resolution: Invalid

I found the problem. 

On the commandNavigationItem, if the destination property is null then the action property is used for page level navigation. 



> <tr:commandNavigationItem
> -------------------------
>
>                 Key: ADFFACES-465
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-465
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.0-incubating-core
>         Environment: Windows XP, Using Exadel IDE
>            Reporter: Jim Dolinski
>
> I have a issue when using the <tr:commandNavigationItem>.
> I have a application that uses the <tr:page> tag. Inside of the tag, I am using the nodestamp facet with a commandNavigationItem. 
> <f:facet name="nodeStamp">
> 	<tr:commandNavigationItem text="#{foo.label}"  
> 					          action="#{foo.getOutcome}"
> 			                  icon="#{foo.ico}"
> 			                  rendered="#{foo.shown}"
> 			                  disabled="#{foo.readOnly}"
>                                           destination=""/>                                  
> </f:facet>                      
> The application is using a menu model to render the menu system. I have two "global" commandNavigationItems that are rendered, "help" and "login". I would like the help to use a external URI (destination) for the help file. All other navigation items will use a action for navigation. When I include the destination property on the component, it will disable any actions from firing (even if it is empty). Is there a way to mix the destination and action properties for "page" navigation? I tried including two commandNavigationItems within the nodestamp facet with no luck. Maybe there is a work around?
> Thanks and Keep up the good work, Jim Dolinski

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.