[
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