[JBoss JIRA] (RF-5707) extendedDataTable: JS error appears when visible="false" for any component column.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-5707?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem updated RF-5707:
------------------------------
Description:
Place rich:column with visible="false" inside extendedDataTable:
{code:title=(test-application/jsp)}
<rich:column id="admissionDate" headerClass="dataTableHeader" visible="fasle"
width="25%" label="Admission date" sortable="true"
sortBy="#{patient.admissionDate}">
<f:facet name="header">
<h:outputText value="Admission date" />
</f:facet>
<h:outputText value="#{patient.admissionDate}" />
</rich:column>
{code}
For more info see attached screenshot with js error.
was:
Place rich:column with visible="false" inside extendedDataTable:
<rich:column id="admissionDate" headerClass="dataTableHeader" visible="fasle"
width="25%" label="Admission date" sortable="true"
sortBy="#{patient.admissionDate}">
<f:facet name="header">
<h:outputText value="Admission date" />
</f:facet>
<h:outputText value="#{patient.admissionDate}" />
</rich:column>(test-application/jsp)
For more info see attached screenshot with js error.
> extendedDataTable: JS error appears when visible="false" for any component column.
> ----------------------------------------------------------------------------------
>
> Key: RF-5707
> URL: https://issues.jboss.org/browse/RF-5707
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.3.0
> Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.GA)
> Reporter: Mikhail Vitenkov
> Priority: Optional
> Fix For: 3.Future
>
> Attachments: edtVisible.png
>
>
> Place rich:column with visible="false" inside extendedDataTable:
> {code:title=(test-application/jsp)}
> <rich:column id="admissionDate" headerClass="dataTableHeader" visible="fasle"
> width="25%" label="Admission date" sortable="true"
> sortBy="#{patient.admissionDate}">
> <f:facet name="header">
> <h:outputText value="Admission date" />
> </f:facet>
> <h:outputText value="#{patient.admissionDate}" />
> </rich:column>
> {code}
> For more info see attached screenshot with js error.
--
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, 12 months
[JBoss JIRA] (RF-11992) cache bug in portlet
by Ken Finnigan (JIRA)
[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ]
Ken Finnigan reassigned RF-11992:
---------------------------------
Assignee: Brian Leathem (was: Ken Finnigan)
Assigning back to you as I think this is now safe to reject/close based on Ivan's last comment
> cache bug in portlet
> --------------------
>
> Key: RF-11992
> URL: https://issues.jboss.org/browse/RF-11992
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 3.3.3.Final, 4.2.0.CR1
> Environment: jboss portal 2.7.2; Gatein portal
> Reporter: Ivan Ravin
> Assignee: Brian Leathem
> Priority: Minor
> Fix For: 5-Tracking
>
>
> On Jboss and Gatein portal richfaces cant be cached when user is logged in.
> Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code.
> The steps for reproduce bug are:
> download portlet bridge 2.2 archive
> deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas)
> look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet.
> When user is not logged in, all richfaces resources are caching well, and this is headers returned by server:
> |Cache-Control |max-age=86400|
> |Content-Type |text/javascript|
> |Date |Thu, 26 Jan 2012 17:57:39 GMT|
> |Expires |27 Jan 2012 17:57:39 GMT|
> |Last-Modified |26 Jan 2012 17:42:17 GMT|
> |Server |Apache-Coyote/1.1|
> |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0|
> But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb).
> This is headers returned by portal 2.7.2 when user logged in:
> |Cache-Control |{color:red}no-cache,{color} max-age=86400|
> |Content-Type |text/javascript|
> |Date |Thu, 26 Jan 2012 18:26:49 GMT|
> |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT|
> |Last-Modified |26 Jan 2012 18:05:56 GMT|
> |{color:red}Pragma{color} |{color:red}No-cache{color}|
> |Server |Apache-Coyote/1.1|
> |Transfer-Encoding |chunked|
> |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0|
> The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header:
> |Cache-Control |max-age=86400|
> |Content-Type |text/javascript;charset=UTF-8|
> |Date |Sat, 28 Jan 2012 08:54:14 GMT|
> |Expires |29 Jan 2012 08:54:14 GMT|
> |Last-Modified |28 Jan 2012 08:51:11 GMT|
> |{color:red}Pragma{color} |{color:red}No-cache{color}|
> |Server |Apache-Coyote/1.1|
> |Transfer-Encoding |chunked|
> |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1|
> This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network.
> I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component.
> In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic.
> To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource headers processing in portal code, like it done in gatein.
--
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, 12 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick regression
by Fab Mars (JIRA)
[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ]
Fab Mars updated RF-12647:
--------------------------
Description:
During my migration from RF 3.3 I found this:
Before (with RF 3.3.3):
{code:xml}
<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}
<rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
<a4j:support event="rowclick" render="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}
But the a4j:aja isn't triggered. To start having something that works, one needs to remove the a4j:param and do it straight.
{code:xml}
<a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
{code}
Not sure this is a regression or not, but wait, here's more: when one clicks on a row with that code, he gets an ArrayIndexOutOfBoundsException 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 declare the <a4j:ajax event="rowclick" /> in the <rich:column/>
Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say it's a regression. Or at least that needs an extra clarification in the documentation and migration guide. Thank you.
was:
During my migration from RF 3.3 I found this:
Before (with RF 3.3.3):
{code:xml}
<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}
<rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
<a4j:support event="rowclick" render="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}
But the a4j:aja isn't triggered. To start having something that works, one needs to remove the a4j:param and do it straight.
{code:xml}
<a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
{code}
Not sure this is a regression or not, but wait, here's more: when one clicks on a row with that code, he gets an ArrayIndexOutOfBoundsException because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself. Hence String rowId = clientId.substring(baseId.length() + 1);
So...to make it work, you have to actually declare the <a4j:ajax event="rowclick" /> in the <rich:column/>
Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say a regression. Or at least that needs an extra clarification in the documentation and migration guide.
> rich:dataTable rowclick regression
> ----------------------------------
>
> 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
>
> During my migration from RF 3.3 I found this:
> Before (with RF 3.3.3):
> {code:xml}
> <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}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:support event="rowclick" render="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}
> But the a4j:aja isn't triggered. To start having something that works, one needs to remove the a4j:param and do it straight.
> {code:xml}
> <a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
> {code}
> Not sure this is a regression or not, but wait, here's more: when one clicks on a row with that code, he gets an ArrayIndexOutOfBoundsException 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 declare the <a4j:ajax event="rowclick" /> in the <rich:column/>
> Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say it's a regression. 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, 12 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick regression
by Fab Mars (JIRA)
[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ]
Fab Mars updated RF-12647:
--------------------------
Summary: rich:dataTable rowclick regression (was: rich:dataTable rowclick changed scope)
> rich:dataTable rowclick regression
> ----------------------------------
>
> 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
>
> During my migration from RF 3.3 I found this:
> Before (with RF 3.3.3):
> {code:xml}
> <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}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:support event="rowclick" render="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}
> But the a4j:aja isn't triggered. To start having something that works, one needs to remove the a4j:param and do it straight.
> {code:xml}
> <a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
> {code}
> Not sure this is a regression or not, but wait, here's more: when one clicks on a row with that code, he gets an ArrayIndexOutOfBoundsException because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself. Hence String rowId = clientId.substring(baseId.length() + 1);
> So...to make it work, you have to actually declare the <a4j:ajax event="rowclick" /> in the <rich:column/>
> Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say a regression. Or at least that needs an extra clarification in the documentation and migration guide.
--
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, 12 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick changed scope
by Fab Mars (JIRA)
Fab Mars created RF-12647:
-----------------------------
Summary: rich:dataTable rowclick changed scope
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
During my migration from RF 3.3 I found this:
Before (with RF 3.3.3):
{code:xml}
<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}
<rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
<a4j:support event="rowclick" render="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}
But the a4j:aja isn't triggered. To start having something that works, one needs to remove the a4j:param and do it straight.
{code:xml}
<a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
{code}
Not sure this is a regression or not, but wait, here's more: when one clicks on a row with that code, he gets an ArrayIndexOutOfBoundsException because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself. Hence String rowId = clientId.substring(baseId.length() + 1);
So...to make it work, you have to actually declare the <a4j:ajax event="rowclick" /> in the <rich:column/>
Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say a regression. Or at least that needs an extra clarification in the documentation and migration guide.
--
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, 12 months
[JBoss JIRA] (RF-12229) Ajax partial response extension tag is not written when render="@all"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12229?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-12229.
-----------------------------
Resolution: Done
> Ajax partial response extension tag is not written when render="@all"
> ---------------------------------------------------------------------
>
> Key: RF-12229
> URL: https://issues.jboss.org/browse/RF-12229
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.2.1.Final
> Environment: RichFaces 4.3.0-SNAPSHOT
> Reporter: Luca Nardelli
> Assignee: Lukáš Fryč
> Fix For: 4.3.0.M3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> * --Partial response extension is not written in f:ajax is one of the causes of RF-12031--
> * Partial response extension is not written if render="@all" (see steps to Reproduce)
> Render all seems a wanted behaviour: ExtendedPartialViewContextImpl.visitActivatorAtRender method
> {code:java}
> if (!isRenderAll()) {
> ...
> if (!Boolean.TRUE.equals(renderAll) && !ids.contains(ALL)) {
> addImplicitRenderIds(ids, limitRender);
> appendOnbeforedomupdate(onbeforedomupdate);
> appendOncomplete(oncomplete);
> setResponseData(responseData);
> }
> }
> {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, 12 months
[JBoss JIRA] (RF-12641) Rich:focus support for mobile browsers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12641?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-12641 at 12/7/12 12:01 PM:
-----------------------------------------------------------
So should this stay included in {{4.3.0.M3}}?
was (Author: lfryc):
So should this stay included in M3?
> Rich:focus support for mobile browsers
> --------------------------------------
>
> Key: RF-12641
> URL: https://issues.jboss.org/browse/RF-12641
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.0.M3
> Reporter: Juraj Húska
> Fix For: 4.3.0.M3
>
>
> The current implementation of {{rich:focus}} works for desktop browsers only.
> It would be nice to have support for mobile devices as well.
> Possible support is to make mobile browser to focus wished input together with showing the keyboard.
--
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, 12 months