3:11 p.m.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that were
not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 p.m.
New subject: [JBoss JIRA] Updated: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Dan Allen updated RF-3273:
--------------------------
Attachment: RF-3273-v1.txt
Uploading concept patch. Likely, the fix should be deeper down to avoid processing the
script and style resources on an Ajax response.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Fix For: 3.2.0.SR1
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 p.m.
New subject: [JBoss JIRA] Updated: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Dan Allen updated RF-3273:
--------------------------
Fix Version/s: 3.2.0.SR1
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Fix For: 3.2.0.SR1
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Resolved: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Nick Belaevski resolved RF-3273.
--------------------------------
Resolution: Rejected
Please see my comment
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Commented: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=comments#action_12410846 ]
Nick Belaevski commented on RF-3273:
------------------------------------
That won't work right for all possible cases, because component subtree that is being
replaced on the client can be modified during AJAX request so that it contains components
that weren't there previously. E.g. components added programmtically, usage of c:if
tags or page included using a4j:include.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Updated: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Nick Belaevski updated RF-3273:
-------------------------------
Fix Version/s: (was: 3.2.0.SR1)
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
New subject: [JBoss JIRA] Commented: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=comments#action_12410850 ]
Dan Allen commented on RF-3273:
-------------------------------
I completely object to this rejection. There *has* to be a way to find a middle ground.
These large Ajax requests are *unacceptable*. It could very well push RichFaces out of our
technology stack. What about the cases when programmatic manipulation is not being used
and c:if is not being used? What about the simpler cases? At the very least there needs to
be a flag in the Ajax4jsf filter configuration or expose the logic so that it can be
overridden by subclassing the filter.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
New subject: [JBoss JIRA] Reopened: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Dan Allen reopened RF-3273:
---------------------------
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Dan Allen
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 a.m.
New subject: [JBoss JIRA] Updated: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Nick Belaevski updated RF-3273:
-------------------------------
Issue Type: Feature Request (was: Bug)
Fix Version/s: Future Versions
Assignee: Alexander Smirnov
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Dan Allen
Assigned To: Alexander Smirnov
Fix For: Future Versions
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:11 a.m.
New subject: [JBoss JIRA] Commented: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=comments#action_12411171 ]
Dan Allen commented on RF-3273:
-------------------------------
I can accept this being a feature request.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Dan Allen
Assigned To: Alexander Smirnov
Fix For: Future Versions
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 p.m.
New subject: [JBoss JIRA] Commented: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=comments#action_12411413 ]
Alexander Smirnov commented on RF-3273:
---------------------------------------
It is wery complex solution to resolve all JavaScript/Styles changes on a page.
For a first versions, Ajax4jsf froject have never sent <head> contant for an ajax
responses. Now it send all references to a scripts and styles, due a lot of bags with the
first solution.
But it is possible to omit head content for a case of Script/Style loading strategy
"ALL", this feature had been added since 3.1.4 release.
It is make sence to skip <head> element content for a such case.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Dan Allen
Assigned To: Alexander Smirnov
Fix For: Future Versions
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 p.m.
New subject: [JBoss JIRA] Work started: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=all ]
Work on RF-3273 started by Alexander Smirnov.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Dan Allen
Assigned To: Alexander Smirnov
Fix For: Future Versions
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:40 p.m.
New subject: [JBoss JIRA] Commented: (RF-3273) Ajax response should not send <head> tag
[ http://jira.jboss.com/jira/browse/RF-3273?page=comments#action_12413275 ]
Alexander Smirnov commented on RF-3273:
---------------------------------------
In the RichFaces 3.2.1 trunk, scripts and styles for a load strategy all/none don't
loaded during AJAX requests.
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: http://jira.jboss.com/jira/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.0
Reporter: Dan Allen
Assigned To: Alexander Smirnov
Fix For: Wishes
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 p.m.
New subject: [JBoss JIRA] Resolved: (RF-3273) Ajax response should not send <head> tag
[
https://jira.jboss.org/browse/RF-3273?page=com.atlassian.jira.plugin.syst...
]
Alexander Smirnov resolved RF-3273.
-----------------------------------
Resolution: Rejected
Ajax response should not send <head> tag
----------------------------------------
Key: RF-3273
URL: https://jira.jboss.org/browse/RF-3273
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0
Reporter: Dan Allen
Assignee: Alexander Smirnov
Fix For: Future
Attachments: RF-3273-v1.txt
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
There is an expectation that Ajax responses are reasonably small. However, RichFaces Ajax
responses are unreasonably large because the BaseXMLFilter is mistakingly sending the
entire <head> tag regardless of whether the response type is Ajax or not. The
<head> tag contains many <script> and <link> tags that bloat the
response. The BaseXMLFilter should only be sending the <head> tag on a normal
response.
Now you might think, "What if the region to be rendered has new components (that
were not previously rendered) for which styles and scripts are necessary for proper
behavior?" Well, RichFaces is already smart and incorporates these styles and scripts
into the initial response even if the associated components are not rendered. So there is
absolutely *no* reason to have them sent in the Ajax response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5293
days inactive
6062
days old
richfaces-issues@lists.jboss.org
13 comments
3 participants
participants (3)
-
Alexander Smirnov (JIRA) -
Dan Allen (JIRA)
-
Nick Belaevski (JIRA)