[TAPESTRY-1605] The request encoding (for component action requests) occurs too late; after query parameters of the request have been accessed, which prevents the proper request encoding from being used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.5
• Fix Version/s: 5.0.11
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: polawat phetra
• Created: 27/Jun/07 01:37
• Updated: 03/Mar/08 10:35
• Resolved: 02/Mar/08 23:13

Description

Due to changeset 550147 that fix issue "tapestry-1294",

request.setCharacterEncoding is not working in case of form submit data event
because of method request.setEncoding in RequestEncodingInitializerImpl is called after
request.getParameter(InternalConstants.PAGE_CONTEXT_NAME) in ComponentActionDispatcher.

Issue Links

• is related to: TAPESTRY-1294 Tapestry does not set an output encoding which prevents Unicode content from being output correctly