Bug 794331 (JBEPP-1376)

Summary:	Text encoding is lost in serveResources
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Portal	Assignee:	Matt Wringe <mwringe>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.1.GA	CC:	epp-bugs, jmorgan, mweiler
Target Milestone:	---
Target Release:	5.2.1.GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1376
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	It was discovered that when content was served from a portlet, the resource encoding was being rewritten with the default encoding of the running JVM. To work around the issue, users had to serve the resource as a binary, or set the system encoding to ISO-8859-1. The fix implements improved resource handling, which honors the mime type encoding when outputting byte array data.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-07 15:48:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Weiler 2011-11-18 12:06:53 UTC

Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008UApw
Workaround Description: 1. Serve the resource as binary
2. Set the default system encoding to ISO-8859-1
project_key: JBEPP

Platform issue for GTNPC-78 Text encoding is lost in serveResources

Comment 2 Martin Weiler 2011-11-18 12:08:17 UTC

Link: Added: This issue depends GTNPC-78

Comment 3 Thomas Heute 2011-11-18 12:31:08 UTC

Tentatively set for 5.2.1

Comment 4 Thomas Heute 2011-12-13 10:30:54 UTC

Release Notes Docs Status: Added: Not Yet Documented
Release Notes Text: Added: When serving content from a portlet, the encoding of the resource gets rewrote with the default encoding of the running JVM

Comment 5 Jared MORGAN 2011-12-13 21:31:43 UTC

Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue
Release Notes Text: Removed: When serving content from a portlet, the encoding of the resource gets rewrote with the default encoding of the running JVM Added: When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1.

Comment 6 Matt Wringe 2012-02-07 15:48:42 UTC

Issue has now been fixed in EPP svn repository and will appear in the next version.

Please note that there are a couple of issues with the example application attached to this jira, so the example application may not work as expected.

Comment 7 Matt Wringe 2012-02-07 15:48:42 UTC

Release Notes Docs Status: Removed: Documented as Known Issue Added: Not Yet Documented
Release Notes Text: Removed: When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. Added: Updated the portlet resource handling to take into consideration the encoding of the mime type when outputting byte array data.

Comment 8 Jared MORGAN 2012-03-27 04:07:38 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
It was discovered that when content was served from a portlet, the resource encoding was being rewritten with the default encoding of the running JVM. To work around the issue, users had to serve the resource as a binary, or set the system encoding to ISO-8859-1. The fix implements improved resource handling, which honors the mime type encoding when outputting byte array data.