Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355500 - RAP application with "standard" client-library variant does not work after 1.5 M1
Summary: RAP application with "standard" client-library variant does not work after 1....
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P1 major (vote)
Target Milestone: 1.5 M2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-23 09:38 EDT by Holger Staudacher CLA
Modified: 2011-08-24 09:36 EDT (History)
3 users (show)

See Also:

Attachments
Error screenshot (90.32 KB, image/png)
2011-08-23 09:39 EDT, Holger Staudacher CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Staudacher CLA 2011-08-23 09:38:37 EDT 
We use the nightly RAP repository to build our nightly build. After deploying the Application to a Tomcat 6 or 7 the application is not accessible via Chrome and Firefox (it works with IE). The error was added in the last days after 1.5 M1 because with the M1 build this does not happen. I will attach a screenshot that displays the error.

* Tested with Windows7,OS X Lion on Tomcat 6 and 7.
Comment 1 Holger Staudacher CLA 2011-08-23 09:39:10 EDT 
Created attachment 201994 [details]
Error screenshot
Comment 2 Ivan Furnadjiev CLA 2011-08-23 10:11:25 EDT 
I can reproduce it with deployed Controls Demo in Tomcat. The error is in the new javascript file EncodingUtil.js. Continue with the investigation.
Comment 3 Ivan Furnadjiev CLA 2011-08-23 10:35:30 EDT 
Reproducible without deployment with Client-Side Library Variant set to "Standard".
Comment 4 Ivan Furnadjiev CLA 2011-08-23 11:19:21 EDT 
The problem is in the special characters \u2028 and \u2029 defined as a keys in the _escapeMap. I think that they should be escaped on the server not on the client, because they lead to an error in the JSON protocol message too. Probably truncateAtZero should be done on the server as well.
Comment 5 Tim Buschtoens CLA 2011-08-24 09:36:55 EDT 
Fixed in CVS HEAD by creating the string with the problematic characters on runtime using String.fromCharCode. For the issue of the the characters breaking the json-message we will open a new bug.