[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing
by John Yeary (JIRA)
John Yeary created RF-12846:
-------------------------------
Summary: a4j:commandLink accesskey attribute missing
Key: RF-12846
URL: https://issues.jboss.org/browse/RF-12846
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.1, 4.2.3.Final, 4.2.2.Final
Reporter: John Yeary
Priority: Minor
The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12845) rich:menuItem does not work as composite component
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-12845?page=com.atlassian.jira.plugin.s... ]
Michael B updated RF-12845:
---------------------------
Description:
When creating a composite component that contains a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector.
{code:xml|title:menuItem.xhtml}
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:rich="http://richfaces.org/rich"
xmlns:composite="http://java.sun.com/jsf/composite">
<composite:interface>
<composite:attribute name="icon" type="java.lang.String" required="false" />
<composite:attribute name="label" type="java.lang.String" required="true" />
<composite:attribute name="menuItem" type="java.lang.String" required="true" />
<composite:attribute name="menuKey" type="java.lang.String" required="true" />
<composite:attribute name="value" type="java.lang.String" required="true" />
</composite:interface>
<composite:implementation>
<rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}">
<f:param name="selectedItem" value="#{cc.attrs.value}" />
</rich:menuItem>
</composite:implementation>
</html>
{code}
Including the resulting composite component in a rich:dropDownMenu like
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails.
See example for comparison - item 2 and 3 are working, while item 1 is not:
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
<rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}">
<f:param name="selectedItem" value="item2" />
</rich:menuItem>
<rich:menuGroup label="Group">
<xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" />
</rich:menuGroup>
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
was:
When creating a composite component that contain a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector.
{code:xml|title:menuItem.xhtml}
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:rich="http://richfaces.org/rich"
xmlns:composite="http://java.sun.com/jsf/composite">
<composite:interface>
<composite:attribute name="icon" type="java.lang.String" required="false" />
<composite:attribute name="label" type="java.lang.String" required="true" />
<composite:attribute name="menuItem" type="java.lang.String" required="true" />
<composite:attribute name="menuKey" type="java.lang.String" required="true" />
<composite:attribute name="value" type="java.lang.String" required="true" />
</composite:interface>
<composite:implementation>
<rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}">
<f:param name="selectedItem" value="#{cc.attrs.value}" />
</rich:menuItem>
</composite:implementation>
</html>
{code}
Including the resulting composite component in a rich:dropDownMenu like
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails.
See example for comparison - item 2 and 3 are working, while item 1 is not:
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
<rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}">
<f:param name="selectedItem" value="item2" />
</rich:menuItem>
<rich:menuGroup label="Group">
<xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" />
</rich:menuGroup>
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
> 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, IE8 + FF19.0.2
> Reporter: Michael B
> Labels: richfaces
>
> When creating a composite component that contains a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector.
> {code:xml|title:menuItem.xhtml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:composite="http://java.sun.com/jsf/composite">
>
> <composite:interface>
> <composite:attribute name="icon" type="java.lang.String" required="false" />
> <composite:attribute name="label" type="java.lang.String" required="true" />
> <composite:attribute name="menuItem" type="java.lang.String" required="true" />
> <composite:attribute name="menuKey" type="java.lang.String" required="true" />
> <composite:attribute name="value" type="java.lang.String" required="true" />
> </composite:interface>
>
> <composite:implementation>
> <rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}">
> <f:param name="selectedItem" value="#{cc.attrs.value}" />
> </rich:menuItem>
> </composite:implementation>
>
> </html>
> {code}
> Including the resulting composite component in a rich:dropDownMenu like
> {code:xml}
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
>
> <rich:toolbar>
> <rich:dropDownMenu>
> <f:facet name="label">
> <h:outputText value="Test" />
> </f:facet>
> <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
> </rich:dropDownMenu>
> </rich:toolbar>
>
> </ui:composition>
> {code}
> ... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails.
> See example for comparison - item 2 and 3 are working, while item 1 is not:
> {code:xml}
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
>
> <rich:toolbar>
> <rich:dropDownMenu>
> <f:facet name="label">
> <h:outputText value="Test" />
> </f:facet>
> <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
> <rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}">
> <f:param name="selectedItem" value="item2" />
> </rich:menuItem>
> <rich:menuGroup label="Group">
> <xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" />
> </rich:menuGroup>
> </rich:dropDownMenu>
> </rich:toolbar>
>
> </ui:composition>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12845) rich:menuItem does not work as composite component
by Michael B (JIRA)
Michael B created RF-12845:
------------------------------
Summary: 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, IE8 + FF19.0.2
Reporter: Michael B
When creating a composite component that contain a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector.
{code:xml|title:menuItem.xhtml}
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:rich="http://richfaces.org/rich"
xmlns:composite="http://java.sun.com/jsf/composite">
<composite:interface>
<composite:attribute name="icon" type="java.lang.String" required="false" />
<composite:attribute name="label" type="java.lang.String" required="true" />
<composite:attribute name="menuItem" type="java.lang.String" required="true" />
<composite:attribute name="menuKey" type="java.lang.String" required="true" />
<composite:attribute name="value" type="java.lang.String" required="true" />
</composite:interface>
<composite:implementation>
<rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}">
<f:param name="selectedItem" value="#{cc.attrs.value}" />
</rich:menuItem>
</composite:implementation>
</html>
{code}
Including the resulting composite component in a rich:dropDownMenu like
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails.
See example for comparison - item 2 and 3 are working, while item 1 is not:
{code:xml}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich"
xmlns:xxx="http://java.sun.com/jsf/composite/xxx">
<rich:toolbar>
<rich:dropDownMenu>
<f:facet name="label">
<h:outputText value="Test" />
</f:facet>
<xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" />
<rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}">
<f:param name="selectedItem" value="item2" />
</rich:menuItem>
<rich:menuGroup label="Group">
<xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" />
</rich:menuGroup>
</rich:dropDownMenu>
</rich:toolbar>
</ui:composition>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ]
Pete Muir commented on RF-12809:
--------------------------------
We have a standard set of BOMs for all product components. I understand this may be more confusing for RichFaces users who aren't used to this, but it is a lot more consistent across the whole product line.
It's easy to update the version in the JBoss BOMs, just send a pull request to that project, and we will do a release. The only reason it's old is because no one from the RichFaces team has requested that it is updated :-)
Whilst it may make the example clearer to you, when viewed across all examples, it's more confusing, IMO as its not consistent.
> Richfaces-related examples should use -with-richfaces BOM
> ---------------------------------------------------------
>
> Key: RF-12809
> URL: https://issues.jboss.org/browse/RF-12809
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Tomas Repel
> Fix For: 4.3.2, 5.0.0.M2
>
>
> There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
Jan Papousek closed RF-11382.
-----------------------------
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-11382:
----------------------------------------------
Jan Papousek <jpapouse(a)redhat.com> made a comment on [bug 916314|https://bugzilla.redhat.com/show_bug.cgi?id=916314]
verified, it works as expected
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months