the content type interceptor determines the content type that the browser requested / can handle. The portal takes this content type as the allowed content type for the current request. Portlets that want to set a particular content type need to first check if the current request supports that content type. Just think about it: if the browser makes a request and the expected content type is text/html, what is the portal supposed to do if one of the portlets returns text/xml ? Or in the reverse: if the request's content type is text/xml and now one of the portlets tries to set it's content type to text/html . What should the portal do? Wrap the fragment in a CDATA section, or ...?
If you want to be able to write text/xml from a portlet, your entire request needs to be rendering text/xml content. This requested content type is, as you correctly stated above, determined by the ContentTypeInterceptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915327#3915327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915327 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
