[JBoss JIRA] (RF-11992) cache bug in portlet
by Ivan Ravin (JIRA)
Ivan Ravin created RF-11992:
-------------------------------
Summary: 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)
Affects Versions: 4.2.0.CR1, 3.3.3.Final
Environment: jboss portal 2.7.2; Gatein portal
Reporter: Ivan Ravin
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 bridge 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.
Gatein portal overwrite 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (RF-10230) New component tracker for 4.X
by Jay Balunas (JIRA)
New component tracker for 4.X
-----------------------------
Key: RF-10230
URL: https://issues.jboss.org/browse/RF-10230
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component
Reporter: Jay Balunas
This is an umbrella jira that can be used to link, and track to new component requests and plans for releases in the 4.X series.
The complete process for handling new component requests, and discussions can be found here <LINK>
When creating a new component jira please link here, or create as a sub-task of this jira.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (RF-11916) extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up.
by Tom Giberius (JIRA)
Tom Giberius created RF-11916:
---------------------------------
Summary: extendedDataTable partial update => extend the functionality with INSERT and DELETE row where scroll position does not go up.
Key: RF-11916
URL: https://issues.jboss.org/browse/RF-11916
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Tom Giberius
Situation:
1) extendDataTable with a verticall ScrollBar
2) Insert or delete record by insert/delete in myBean and by a re-render of the table.
3) The re-render causes a full rebuild of the table in the DOM and the effect is that the scrollbar goes up to the beginning.In fact this makes a scrollable extendedDataTable not useful for inserting/deleting records.
Partial Table Render for extendedDataTable is available in RF 4.1 with a construction like:
render="myTable@rows(myBean.listOfUpdateRows):myColumn"
This works fine for already available rows and indeed it is an UPDATE.
Also @body, @header and @footer are available for partial table update.
I would like to hava a kind of partitial table INSERT and UPDATE where not the whole table is "re-draw" by only the record(s) are INSERTED or DELETED and where the scroll position for the user visually stays the same.
It could look like:
render="myTable(a)insert(myBean.Row)
render="myTable(a)delete(myBean.RowKey)
If you have questions I will gladly elaborate on above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years