[JBoss JIRA] (RF-12944) Rerender problem on popup panel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12944?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12944.
--------------------------------
Labels: (was: waiting_on_user)
Resolution: Incomplete Description
> Rerender problem on popup panel
> -------------------------------
>
> Key: RF-12944
> URL: https://issues.jboss.org/browse/RF-12944
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.2.2.Final
> Reporter: András Bognár
> Assignee: Juraj Húska
>
> Some page what we made, it contains popup panel. The method which shows the popup is like this:
> {code}
> <a4j:commandButton
> styleClass="standardButton"
> value="#{property.someThing}"
> action="#{bean.action}"
> render="contentClientId"
> oncomplete="#{rich:component('panelName')}.show();"/>
> {code}
> but after showing the popup contains old data and 1-2 seconds later refresh and we can see the correct data.
--
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
11 years, 3 months
[JBoss JIRA] (RF-12779) dropdown menu onclick event
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12779?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12779:
-------------------------------
Labels: (was: waiting_on_user)
> dropdown menu onclick event
> ---------------------------
>
> Key: RF-12779
> URL: https://issues.jboss.org/browse/RF-12779
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: microsoft xp
> Reporter: Deepak Salve
>
> In my project i have toolbar.
> On that toolbar I have added 4 menus.
> in that 4 menus 2 menu have sub menu items and working fine.
> but for other, they dont have submenu.
> i want to navigate to other page on clicking that menu itself.
> but currently there is no onclick event so how should manage that click operation.
--
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
11 years, 3 months
[JBoss JIRA] (RF-12779) dropdown menu onclick event
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12779?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12779.
--------------------------------
Resolution: Incomplete Description
> dropdown menu onclick event
> ---------------------------
>
> Key: RF-12779
> URL: https://issues.jboss.org/browse/RF-12779
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: microsoft xp
> Reporter: Deepak Salve
> Labels: waiting_on_user
>
> In my project i have toolbar.
> On that toolbar I have added 4 menus.
> in that 4 menus 2 menu have sub menu items and working fine.
> but for other, they dont have submenu.
> i want to navigate to other page on clicking that menu itself.
> but currently there is no onclick event so how should manage that click operation.
--
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
11 years, 3 months
[JBoss JIRA] (RF-12660) Second call of jsFunction inside dataTable does reach an action
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12660?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12660:
-------------------------------
Labels: regression (was: regression waiting_on_user)
> Second call of jsFunction inside dataTable does reach an action
> ---------------------------------------------------------------
>
> Key: RF-12660
> URL: https://issues.jboss.org/browse/RF-12660
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final
> Environment: Windows 7, Tomcat 6
> Reporter: Andrei Tikhomirov
> Labels: regression
>
> jsFunction works correclty only for the row clicked at first.
> For second and other rows _onbegin_ fires, but _action_ and _oncomplete_ are not executed.
> POST request is executed.
> It worked for me on 4.0.0.Final and does not work after migration on 4.2.2.Final
> Reproduced on 4.2.3.Final
> {code}
> <rich:column>
> <span id="toggler#{row.id}" onclick="click(#{row.id});">
> <rich:collapsibleSubTableToggler for="subtbl" rendered="true"
> expandedIcon="/images/minus.png"
> collapsedIcon="/images/plus.png" />
> <a4j:jsFunction name="readFeeadbackMessage#{row.id}"
> onbegin="unbindFeedbackMessageClick(#{row.id});"
> action="#{bean.action(row.id)}"
> oncomplete="complete(#{row.id})"/>
> </span>
> ...........
> </rich:column>
> {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
11 years, 3 months
[JBoss JIRA] (RF-12660) Second call of jsFunction inside dataTable does reach an action
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12660?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12660.
--------------------------------
Resolution: Incomplete Description
> Second call of jsFunction inside dataTable does reach an action
> ---------------------------------------------------------------
>
> Key: RF-12660
> URL: https://issues.jboss.org/browse/RF-12660
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final
> Environment: Windows 7, Tomcat 6
> Reporter: Andrei Tikhomirov
> Labels: regression
>
> jsFunction works correclty only for the row clicked at first.
> For second and other rows _onbegin_ fires, but _action_ and _oncomplete_ are not executed.
> POST request is executed.
> It worked for me on 4.0.0.Final and does not work after migration on 4.2.2.Final
> Reproduced on 4.2.3.Final
> {code}
> <rich:column>
> <span id="toggler#{row.id}" onclick="click(#{row.id});">
> <rich:collapsibleSubTableToggler for="subtbl" rendered="true"
> expandedIcon="/images/minus.png"
> collapsedIcon="/images/plus.png" />
> <a4j:jsFunction name="readFeeadbackMessage#{row.id}"
> onbegin="unbindFeedbackMessageClick(#{row.id});"
> action="#{bean.action(row.id)}"
> oncomplete="complete(#{row.id})"/>
> </span>
> ...........
> </rich:column>
> {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
11 years, 3 months
[JBoss JIRA] (RF-12694) <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12694:
-------------------------------
Labels: richfaces (was: richfaces waiting_on_user)
> <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
> ----------------------------------------------------------------------------------------
>
> Key: RF-12694
> URL: https://issues.jboss.org/browse/RF-12694
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.2.3.Final
> Environment: Tested in Galssfish3.1 and WAS8
> Reporter: Srinivas Reddy Malipeddi
> Priority: Minor
> Labels: richfaces
>
> When rich component like <rich:dropDownMenu is used, throwing warning"
> {quote}
> com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed.
> {quote}
> Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars
> My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming.
> {code:title=index.xhtml}
> <?xml version="1.0" encoding="UTF-8" ?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
>
> </h:head>
> <h:body>
> <rich:dropDownMenu label="IT Asset">
> <rich:menuItem label="Search" />
> <rich:menuItem label="Create" />
> </rich:dropDownMenu>
> </h:body>
> </ui:composition>
> {code}
> {code:title=Web.xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="3.0"
> xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
> <display-name>TestWeb</display-name>
> <context-param>
> <description>
> The location where state information is saved.
> Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
> saved as a hidden field in the form.
> Default is server.</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
> <context-param>
> <description>
> Comma-delimited list of context-relative resource paths under which the JSF implementation
> will look for application configuration resources, before loading a configuration resource
> named /WEB-INF/faces-config.xml (if such a resource exists).</description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value></param-value>
> </context-param>
> <context-param>
> <description>
> The default suffix for extension-mapped resources that contain JSF components.
> Default is '.jsp'.</description>
> <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
> <param-value>.xhtml</param-value>
> </context-param>
> <context-param>
> <description>
> A human readable string describing where this particular JSF application is
> in the software development lifecycle.
> Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'.
> Default is 'Production'.
> This parameter is not available in JSF 1.x.</description>
> <param-name>javax.faces.PROJECT_STAGE</param-name>
> <param-value>Development</param-value>
> </context-param>
> <context-param>
> <description>
> Monitors Faces JSP files for modifications and synchronizes a running server with
> the changes without restarting the server. If this parameter is set to false or
> removed from the deployment descriptor, any changes made to Faces JSP files may
> not be seen by the server until it is restarted. This parameter is usually set
> to true while the Faces JSP files are being developed and debugged in order to
> improve the performance of the development environment.</description>
> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
> <param-value>true</param-value>
> </context-param>
> <context-param>
> <description>
> Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
> JSF runtime will be loaded and initialized when the first JSF request is processed.
> This may disable custom JSF extensions, such as factories defined in the project.</description>
> <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
> <param-value>true</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>-1</load-on-startup>
> <enabled>true</enabled>
> <async-supported>false</async-supported>
> </servlet>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.xhtml</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> *.faces</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> /faces/*</url-pattern>
> </servlet-mapping>
> <welcome-file-list>
> <welcome-file>index.xhtml</welcome-file>
> </welcome-file-list>
> </web-app>
> {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
11 years, 3 months
[JBoss JIRA] (RF-12660) Second call of jsFunction inside dataTable does reach an action
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12660?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12660:
------------------------------------
Try placing the jsFunction outside of your dataTable, and passing it the relevant parameters (using the a4j:param tag).
> Second call of jsFunction inside dataTable does reach an action
> ---------------------------------------------------------------
>
> Key: RF-12660
> URL: https://issues.jboss.org/browse/RF-12660
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final
> Environment: Windows 7, Tomcat 6
> Reporter: Andrei Tikhomirov
> Labels: regression, waiting_on_user
>
> jsFunction works correclty only for the row clicked at first.
> For second and other rows _onbegin_ fires, but _action_ and _oncomplete_ are not executed.
> POST request is executed.
> It worked for me on 4.0.0.Final and does not work after migration on 4.2.2.Final
> Reproduced on 4.2.3.Final
> {code}
> <rich:column>
> <span id="toggler#{row.id}" onclick="click(#{row.id});">
> <rich:collapsibleSubTableToggler for="subtbl" rendered="true"
> expandedIcon="/images/minus.png"
> collapsedIcon="/images/plus.png" />
> <a4j:jsFunction name="readFeeadbackMessage#{row.id}"
> onbegin="unbindFeedbackMessageClick(#{row.id});"
> action="#{bean.action(row.id)}"
> oncomplete="complete(#{row.id})"/>
> </span>
> ...........
> </rich:column>
> {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
11 years, 3 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick with nested f:param
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12647:
------------------------------------
h5. Regarding "RF 4 Sample 1"
It is a JSF 2 spec limitation that you cannot nest components in a JSF Behaviour, or rather, that nesting components in a behaviour changes the target of that behaviour. There is a spec issue filed addressing this, be sure to vote for it:
* https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-742
* (along with the initiaitng mojarra bug: https://java.net/jira/browse/JAVASERVERFACES-1532)
----
h5. Regarding "RF 4 Sample 2"
The relevant code snippet:
{code}
<a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
{code}
This *should* work. A google search quickly shows one how many people expect it to work. I dug in to find out _why_ it doesn't work:
When a HTML element triggers an ajax event, a check is performed on the server-side to see if the HTML element that triggered the event is the JSF component that is being decoded. This is done in this line of code:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
{code}
if (behaviorSource != null && behaviorSource.equals(clientId)) {
...
{code}
Before the request is sent to the server, we check if the originating element of an event is from a component, and "re-target" it if not (see:RF-12616, RF-12715). This is done in this line of code:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/res...
``
This re-targeting works well, as for the most part elements DOM ids within components use the _#\{clientId}Qualifier_ syntax. However this breaks down with table rows, where the ":" separator is used. This is the same separator used to separate JSF component id's in the clientId. For example, a table with the clilentId "form:edt" will have rows with DOM id "myForm:edt:5:n".
So we need to fix the client-side re-targeting to work for table rows.
[~fabmars] Would you mind filing a new issue to rack this? This issue has several "issues" wrapped within it. Then we can close this issue and move forward solving the specific problem that arose from this report.
----
h5. Regarding "RF 4 Sample 3"
Using the _a4j:jsFunction_ is indeed the currently promoted workaround to meet this use case.
> 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
11 years, 3 months
[JBoss JIRA] (RF-13124) RichFaces is undefined, a4j is undefined, ModalPanel is undefined JS error
by Leonardo Duarte (JIRA)
[ https://issues.jboss.org/browse/RF-13124?page=com.atlassian.jira.plugin.s... ]
Leonardo Duarte commented on RF-13124:
--------------------------------------
Also experience this problem on Weblogic 12c, any ideas on how to avoid this problem (multiple re-deploys) would be appreciated.
> RichFaces is undefined, a4j is undefined, ModalPanel is undefined JS error
> --------------------------------------------------------------------------
>
> Key: RF-13124
> URL: https://issues.jboss.org/browse/RF-13124
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 3.3.3.Final
> Environment: Sun Solaris Operating System
> Java 1.6
> Weblogic 10.3.5 cluster, Load Balance by Apache server with Weblogic loadbalancer pluginiexpl
> Reporter: Azad Akbar
> Labels: richfaces
> Fix For: 3.Future
>
>
> We often get these errors after a restart or redeploy of application on Weblogic 10.3.5 server
> The error is, a4j is undefined, ModalPanel is undefined, RichFaces is undefined JS errors.
>
> The Weblogic is a cluster with two Managed Servers.
> The error comes from only on of the Managed Server, whereas the other one is working fine.
>
> Load Balancer is Apache server with plugin for load balancing Weblogic servers.
>
> This issue happens especially after a restart of the Weblogic servers or Redeploy of applications on the Weblogic servers.
> The solution is strangely "Do a restart with purge cache, followed by redeploy of the application"
> Could this be because the path to the file that contains these javascript objects/variables is generated by some filter in RichFaces and attached to the header of the rendered xhtml page but the RichFaces code fails to put the file on the server path. Or maybe the browser mistakenly starts sending the request to the other server with this path information that was sent from the server 1 of the cluster.
> Or would it be because the application is not getting properly deployed on the Weblogic servers, since the issue goes away after redeployment.
>
> The version of RichFaces is 3.3.3 Final
> Please note that we have enabled sticky session on the Apache LoadBalancer.
--
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
11 years, 3 months