[JBoss JIRA] (RF-13168) JSF component disappears on refresh using a4j:poll
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ]
Brian Leathem moved WFLY-1981 to RF-13168:
------------------------------------------
Project: RichFaces (was: WildFly)
Key: RF-13168 (was: WFLY-1981)
Affects Version/s: (was: 8.0.0.Beta1)
Component/s: compatibility
component-a4j-core
(was: JSF)
(was: Web (Undertow))
Security: Public
> JSF component disappears on refresh using a4j:poll
> --------------------------------------------------
>
> Key: RF-13168
> URL: https://issues.jboss.org/browse/RF-13168
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility, component-a4j-core
> Reporter: Frank Langelage
> Assignee: Brian Leathem
> Labels: interop, jsf22
> Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac
>
>
> On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable.
> This does not work with WildFly build from current sources.
> Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow.
> I'll attach a small project showing the problem.
> The mojarra datatable works fine, is refreshed every 10 seconds.
> The openfaces datatable below disappears on first refresh.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13168) JSF component disappears on refresh using a4j:poll
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13168:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
> JSF component disappears on refresh using a4j:poll
> --------------------------------------------------
>
> Key: RF-13168
> URL: https://issues.jboss.org/browse/RF-13168
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility, component-a4j-core
> Reporter: Frank Langelage
> Assignee: Brian Leathem
> Labels: interop, jsf22
> Fix For: 5.0.0.Alpha3
>
> Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac
>
>
> On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable.
> This does not work with WildFly build from current sources.
> Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow.
> I'll attach a small project showing the problem.
> The mojarra datatable works fine, is refreshed every 10 seconds.
> The openfaces datatable below disappears on first refresh.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13162) Add support for the default-behavior faces-config property-extension to the CDK @Attribute annotation
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13162?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13162:
------------------------------------
I've reverted the commit introducing aupport for the default-behavior. When this issue is revisited, we should investigate how to generate/consume faces-config.xml files using the existing default event capabilities of the CDK model.
The two *-props.xml files that referenced the default-behavior tag are:
https://github.com/richfaces/richfaces-cdk/blob/4.5.0.Alpha1/attributes/s...
https://github.com/richfaces/richfaces-cdk/blob/4.5.0.Alpha1/attributes/s...
The RichFaces components that referenced these property files are:
# AbstractCommandLink.java
# AbstractCommandButton.java
> Add support for the default-behavior faces-config property-extension to the CDK @Attribute annotation
> -----------------------------------------------------------------------------------------------------
>
> Key: RF-13162
> URL: https://issues.jboss.org/browse/RF-13162
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5-Tracking
>
>
> Consider the xml component property definition:
> {code:title=From command-button-props.xml}
> <property>
> <description>
> Javascript code executed when a pointer button is clicked over this element.
> </description>
> <display-name>Button Click Script</display-name>
> <icon />
> <property-name>onclick</property-name>
> <property-class>java.lang.String</property-class>
> <property-extension>
> <cdk:pass-through>false</cdk:pass-through>
> <cdk:event-name default="true">click</cdk:event-name>
> <cdk:event-name>action</cdk:event-name>
> <default-behavior>true</default-behavior>
> </property-extension>
> </property>
> {code}
> There is currently no way to define this using the CDK @Attribute annotation - the _<default-behavior>_ annotation property is absent.
> To resolve this issue (blocking RF-12952) we need to add support for specifying the _default-behavior_ to the @Attribute annotation.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13162) Add support for the default-behavior faces-config property-extension to the CDK @Attribute annotation
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13162?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13162:
-------------------------------
Fix Version/s: 5-Tracking
(was: cdk-4.5.0.Alpha2)
> Add support for the default-behavior faces-config property-extension to the CDK @Attribute annotation
> -----------------------------------------------------------------------------------------------------
>
> Key: RF-13162
> URL: https://issues.jboss.org/browse/RF-13162
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5-Tracking
>
>
> Consider the xml component property definition:
> {code:title=From command-button-props.xml}
> <property>
> <description>
> Javascript code executed when a pointer button is clicked over this element.
> </description>
> <display-name>Button Click Script</display-name>
> <icon />
> <property-name>onclick</property-name>
> <property-class>java.lang.String</property-class>
> <property-extension>
> <cdk:pass-through>false</cdk:pass-through>
> <cdk:event-name default="true">click</cdk:event-name>
> <cdk:event-name>action</cdk:event-name>
> <default-behavior>true</default-behavior>
> </property-extension>
> </property>
> {code}
> There is currently no way to define this using the CDK @Attribute annotation - the _<default-behavior>_ annotation property is absent.
> To resolve this issue (blocking RF-12952) we need to add support for specifying the _default-behavior_ to the @Attribute annotation.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13167) disabled dropDownMenu is missing styleClass
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13167?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13167:
------------------------------------
[~christoph_w] I agree with your assessment, and you have identified the correct place for a fix. Would you like to formulate this as a github pull request?
https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA
(don't forget to sign the CLA: https://cla.jboss.org/)
> disabled dropDownMenu is missing styleClass
> -------------------------------------------
>
> Key: RF-13167
> URL: https://issues.jboss.org/browse/RF-13167
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Reporter: Christoph W.
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
> Comment from attribute styleClass: ??"Space-separated list of CSS style class(es) to be applied when this element is rendered."??
> Also a disabled component may be rendered (otherwise styling wont matter).
> It is easy to fix. How to:
> DropDownMenuRenderer.doEncodeEnd(...) contains following line:
> {{String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";}}
> If component is disabled styleClass must be added also.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13167) disabled dropDownMenu is missing styleClass
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13167?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13167:
-------------------------------
Fix Version/s: 5-Tracking
> disabled dropDownMenu is missing styleClass
> -------------------------------------------
>
> Key: RF-13167
> URL: https://issues.jboss.org/browse/RF-13167
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Reporter: Christoph W.
> Fix For: 5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
> Comment from attribute styleClass: ??"Space-separated list of CSS style class(es) to be applied when this element is rendered."??
> Also a disabled component may be rendered (otherwise styling wont matter).
> It is easy to fix. How to:
> DropDownMenuRenderer.doEncodeEnd(...) contains following line:
> {{String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";}}
> If component is disabled styleClass must be added also.
--
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
10 years, 8 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick with nested f:param
by Fab Mars (JIRA)
[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ]
Fab Mars commented on RF-12647:
-------------------------------
TO make a long story short: You did right.
> rich:dataTable rowclick with nested f:param
> -------------------------------------------
>
> Key: RF-12647
> URL: https://issues.jboss.org/browse/RF-12647
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.0.M2
> Environment: Win7, JDK7, Glassfish3, Mojarra 2.1.14, SeamFaces, RF 4.x.x
> Reporter: Fab Mars
> Labels: waiting_on_user
>
> During my migration from RF 3.3 I found this:
> Before (with RF 3.3.3):
> {code:xml|title="RF 3 Sample"}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:support event="onRowClick" reRender="shippingEditForm">
> <a4j:actionparam name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/>
> </a4j:support>
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> There was nothing really impacting on the migration guide
> https://community.jboss.org/wiki/RichFacesMigrationGuide33x-4xMigration-C...
> So I logically did that with RF4.x.x:
> {code:xml|title="RF 4 Sample 1"}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:ajax event="rowclick" render="shippingEditForm">
> <a4j:param name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/>
> </a4j:ajax>
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> But the a4j:ajax isn't triggered (not at all, it's NOT a param assignment issue). To start having something that responds, one needs to remove the a4j:param and do it EL-newlook style.
> {code:xml|title="RF 4 Sample 2"}
> <a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
> {code}
> Anyhow we're close to RF-11446 and whenever that one gets fixed, one should check whether this case here is also solved.
> But wait, even that doesn't work: when one clicks on a row with that code, the listener is called but an ArrayIndexOutOfBoundsException is thrown because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself, NOT this of the row/cell. Hence, String rowId = clientId.substring(baseId.length() + 1) ends up tragically.
> So...to make it really work, you have to do what's described here: https://community.jboss.org/thread/174063 and not fall into the trap of RF-11446.
> Working code (RF 4.2.3+)
> {code:xml|title="RF 4 Sample 3"}
> <a4j:jsFunction name="shippingListRowClick" render="shippingEditForm">
> <a4j:param name="shippingId" assignTo="#{shippingEdit.id}"/>
> </a4j:jsFunction>
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping" onrowclick="shippingListRowClick(#{shipping.id});">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> All that...for that.
> Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say we have a couple of regressions. Or at least that needs an extra clarification in the documentation and migration guide. Thank you.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13167) disabled dropDownMenu is missing styleClass
by Christoph W. (JIRA)
[ https://issues.jboss.org/browse/RF-13167?page=com.atlassian.jira.plugin.s... ]
Christoph W. updated RF-13167:
------------------------------
Description:
We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
Comment from attribute styleClass: ??"Space-separated list of CSS style class(es) to be applied when this element is rendered."??
Also a disabled component may be rendered (otherwise styling wont matter).
It is easy to fix. How to:
DropDownMenuRenderer.doEncodeEnd(...) contains following line:
{{String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";}}
If component is disabled styleClass must be added also.
was:
We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
Comment from attribute styleClass: "Space-separated list of CSS style class(es) to be applied when this element is rendered."
Also a disabled component may be rendered (otherwise styling wont matter).
It is easy to fix. How to:
DropDownMenuRenderer.doEncodeEnd(...) contains following line:
String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";
If component is disabled styleClass must be added also.
> disabled dropDownMenu is missing styleClass
> -------------------------------------------
>
> Key: RF-13167
> URL: https://issues.jboss.org/browse/RF-13167
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Reporter: Christoph W.
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
> Comment from attribute styleClass: ??"Space-separated list of CSS style class(es) to be applied when this element is rendered."??
> Also a disabled component may be rendered (otherwise styling wont matter).
> It is easy to fix. How to:
> DropDownMenuRenderer.doEncodeEnd(...) contains following line:
> {{String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";}}
> If component is disabled styleClass must be added also.
--
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
10 years, 8 months
[JBoss JIRA] (RF-13167) disabled dropDownMenu is missing styleClass
by Christoph W. (JIRA)
Christoph W. created RF-13167:
---------------------------------
Summary: disabled dropDownMenu is missing styleClass
Key: RF-13167
URL: https://issues.jboss.org/browse/RF-13167
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-menu
Affects Versions: 4.3.3
Reporter: Christoph W.
We use rich:dropDownMenu with attributes disabled and styleClass. But when disabled is false then styleClass is not applied. Using classes for styling via CSS is a must, also for disabled components.
Comment from attribute styleClass: "Space-separated list of CSS style class(es) to be applied when this element is rendered."
Also a disabled component may be rendered (otherwise styling wont matter).
It is easy to fix. How to:
DropDownMenuRenderer.doEncodeEnd(...) contains following line:
String value = "rf-ddm-lbl " + convertToString((isDisabled ? "rf-ddm-dis" : ("rf-ddm-unsel " + styleClass))) + " ";
If component is disabled styleClass must be added also.
--
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
10 years, 8 months