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

Bug 264929

Summary: Provide workaround for invalid XML characters on retrieving Trac tasks via XML-RPC
Product: z_Archived Reporter: Jörg Thönnes <jtk499>
Component: MylynAssignee: Mylyn Inbox <mylyn-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: minor    
Priority: P3 Keywords: helpwanted
Version: 3.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Jörg Thönnes CLA 2009-02-14 06:25:05 EST
If the description or the comment of a Trac task contains binary characters, ie @\001@,
the retrieval of the task data fails with the error message:

bq. 
An invalid XML character (Unicode: 0x1) was found in the element content of the document.

Only the task data up to the bad comment is retrieved.

If the wrong encoding is done by the Trac XML-RPC plugin, this should be correct there.
But it would be good if the Mylyn connector could a bit more tolerant and workaround these
encoding errors.
Comment 1 Steffen Pingel CLA 2009-06-15 02:30:50 EDT
I agree that this should be handled more gracefully. I'll track this on bug 236034 which requests the same feature for JIRA. This needs to addressed on the framework level.

*** This bug has been marked as a duplicate of bug 236034 ***