Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347176

Summary:	R4E cannot handle file path with invalid URI characters
Product:	z_Archived	Reporter:	Sebastien Dubois <sebastien.dubois>
Component:	Mylyn	Assignee:	Project Inbox <r4e-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	0.9
Hardware:	All
OS:	All
Whiteboard:

Description Sebastien Dubois

2011-05-25 11:23:26 EDT

Currently it is impossible to use file path that contain invalid URI characters in R4E.  For example this means that no review groups or rule sets can be created in folders thst e.g. have apces in their names.  This is not acceptable and will need to be fixed ASAP.  I temporarly prevent users to use such folers/files for now, but it will need to be supported

Comment 1 Alvaro Sanchez-Leon

2011-05-25 15:50:13 EDT

Creating a URI from a string with special characters (e.g. spaces) in
the path get encoded e.g. space -> %20. 

A couple of considerations are needed:
1) Preserving the URI as string shall remove /decode (i.e. URI.decode()) the special
characters so a later conversion (i.e. string to URI can successfully re-build the URI).

2) Using the URI device path string to create a File / Resource shall also make sure
to decode the URI to replace special encoded characters in the path.

Using the URI towards EMF for creation of Resource sets does not need any special actions on the special characters and behaves as expected.

The two actions above are now implemented and pushed.