[ http://jira.jboss.com/jira/browse/JBPORTAL-209?page=history ]
Julien Viet resolved JBPORTAL-209:
----------------------------------
Resolution: Done
The bug is fixed and I have added a test case for it.
> setContentType() with encoding not supported
> --------------------------------------------
>
> Key: JBPORTAL-209
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-209
> Project: JBoss Portal
> Type: Bug
> Components: Portal Core
> Versions: 2.0 Beta 1, 2.0 Final, 2.0 Beta 2
> Reporter: Martin Holzner
> Assignee: Julien Viet
> Fix For: 2.0 Beta 1, 2.0 Final, 2.0 Beta 2
>
> Original Estimate: 5 minutes
> Remaining: 5 minutes
>
> it is perfectly legal in a portlet to set the content type like
> "text/html; charset=UTF-8"
> the current implementation of RenderResponse
> (org.jboss.portal.portlet.impl.RenderResponseImpl) does a String comparison
> of the set content type with the content types from the portlet.xml
> descriptor, which obviously fails
> PLT.12.3.1 Content Type states:
> "The portlet container should ignore any character
> encoding specified as part of the content type."
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
