From jira-events at lists.jboss.org Sun Apr 27 12:23:09 2008 Content-Type: multipart/mixed; boundary="===============1263216572403521504==" MIME-Version: 1.0 From: Dan Allen (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-3273) Ajax response should not send tag Date: Sun, 27 Apr 2008 12:23:08 -0400 Message-ID: <22520626.1209313388905.JavaMail.jira@cloud.prod.atl2.jboss.com> In-Reply-To: 13072822.1209240668790.JavaMail.jira@cloud.prod.atl2.jboss.com --===============1263216572403521504== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ http://jira.jboss.com/jira/browse/RF-3273?page=3Dcomments#action_1241= 0850 ] = = Dan Allen commented on RF-3273: ------------------------------- I completely object to this rejection. There *has* to be a way to find a mi= ddle ground. These large Ajax requests are *unacceptable*. It could very we= ll push RichFaces out of our technology stack. What about the cases when pr= ogrammatic 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 overrid= den by subclassing the filter. > Ajax response should not send 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 tag regardless of whether the res= ponse type is Ajax or not. The tag contains many