From jira-events at lists.jboss.org Wed May 1 19:07:53 2013 Content-Type: multipart/mixed; boundary="===============0888016132460910007==" MIME-Version: 1.0 From: Brian Leathem (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] (RF-12845) rich:menuItem does not work as composite component Date: Wed, 01 May 2013 19:07:53 -0400 Message-ID: In-Reply-To: JIRA.12487309.1363364774000@jira02.app.mwc.hst.phx2.redhat.com --===============0888016132460910007== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/RF-12845?page=3Dcom.atlassian.jira.p= lugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12845: ------------------------------- Fix Version/s: 5-Tracking = > rich:menuItem does not work as composite component > -------------------------------------------------- > > Key: RF-12845 > URL: https://issues.jboss.org/browse/RF-12845 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) = > Components: component-menu > Affects Versions: 4.3.1 > Environment: Win7 x64, Java 6 x64, Tomcat 7.0.30 x64, RF 4.3.1, I= E8 + FF19.0.2 > Reporter: Michael B > Priority: Minor > Labels: richfaces > Fix For: 5-Tracking > > > When creating a composite component that contains a rich:menuItem, the me= nu item is not showing. =3D> Client side error while identifying the menu i= tems parent via css-selector. > {code:xml|title:menuItem.xhtml} > > > xmlns:h=3D"http://java.sun.com/jsf/html" > xmlns:f=3D"http://java.sun.com/jsf/core" > xmlns:rich=3D"http://richfaces.org/rich" > xmlns:composite=3D"http://java.sun.com/jsf/composite"> > = > > > > > > > > = > > > > > > = > > {code} > Including the resulting composite component in a rich:dropDownMenu like = > {code:xml} > xmlns:ui=3D"http://java.sun.com/jsf/facelets" > xmlns:h=3D"http://java.sun.com/jsf/html" > xmlns:f=3D"http://java.sun.com/jsf/core" > xmlns:a4j=3D"http://richfaces.org/a4j" > xmlns:rich=3D"http://richfaces.org/rich" > xmlns:xxx=3D"http://java.sun.com/jsf/composite/xxx"> > = > > > > > > > > > = > > {code} > ... reproduces the problem. Writing the rich:menuItem directly inside the= rich:dropDownMenu works. Also wrapping the composite component with rich:m= enuGroup works. Only the direct child option fails. > See example for comparison - item 2 and 3 are working, while item 1 is no= t: > {code:xml} > xmlns:ui=3D"http://java.sun.com/jsf/facelets" > xmlns:h=3D"http://java.sun.com/jsf/html" > xmlns:f=3D"http://java.sun.com/jsf/core" > xmlns:a4j=3D"http://richfaces.org/a4j" > xmlns:rich=3D"http://richfaces.org/rich" > xmlns:xxx=3D"http://java.sun.com/jsf/composite/xxx"> > = > > > > > > > > > > > > > > > = > > {code} > On a side not: just found out, that the problem might come from the rich:= dropDownMenu only allowing for direct children of type rich:menuGroup or ri= ch:menuItem, while a composite component always adds another UIPanel to wra= p itself. So if I understand the concept correctly, one would have to write= a custom component class that is a menu item and also implements NamingCon= tainer and add it as 'componentType' to the interface. Kinda beats the purp= ose of being able to easily create an extended markup for components that a= re expected as direct children though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira --===============0888016132460910007==--