[MAGNOLIA-442] setCharacter encoding Created: 14/Jun/05  Updated: 16/Jun/05  Resolved: 15/Jun/05

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.1 Final
Fix Version/s: 2.1 Final

Type: Bug Priority: Major
Reporter: Nicolas Modrzyk Assignee: Boris Kraft
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X - Jetty 5 - Magnolia SVN (Tuesday June 14th - 1am GMT)


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

getReader() or getInputStream() called

java.lang.IllegalStateException: getReader() or getInputStream() called
at org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(ServletHttpRequest.java:602)
at info.magnolia.cms.servlets.MVCServlet.doGet(MVCServlet.java:82)

Happens when creating a paragraph in admin mode.

Also the same code is called in the export xml servlet.

Commenting out the call to setCharacterEncoding will make everything working fine.



 Comments   
Comment by Philipp Bracher [ 15/Jun/05 ]

I added a try catch with writing a log message. I didn't remove the line since this is used in some cases (see comment in the code)

Comment by Nicolas Modrzyk [ 16/Jun/05 ]

Thanks for the fix !

The same code is still in the export/import servlet (class: info.magnolia.cms.servlets.ImportExportServlet at line 75) ...
Can we add a try catch on that one too ?

Generated at Mon Feb 12 03:17:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.