History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-6550
Type: Bug Bug
Status: Verified Verified
Priority: Major Major
Assignee: Unassigned
Reporter: Myrna van Lunteren
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

if text contains 0x14 character, cdata in xml based on this will be badly formed

Created: 03/May/05 05:47 PM   Updated: 16/Apr/07 03:38 AM
Component/s: Plugins - Issue Views
Affects Version/s: 3.6.3
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File one_JIRA_ISSUE.txt (6 kb)
2. Text File one_JIRA_ISSUE.txt2 (0.3 kb)
3. XML File one_JIRA_ISSUE.xml (10 kb)

Issue Links:
Reference
 

Participants: Daniel Hurst, Myrna van Lunteren and Scott Farquhar [Atlassian]
Since last comment: 91 weeks, 2 days ago
Labels:


 Description  « Hide
When the string in a field has unusual characters - for example Unicode 0x14 - the XML generated will be malformed & will result in a parseException with any browser set up to handle XML.

For instance, Apache Derby issue 246
http://issues.apache.org/jira/browse/DERBY-246?decorator=none&view=rss
results in the following display:
XML Parsing Error: not well-formed
Location: http://issues.apache.org/jira/browse/DERBY-246?decorator=none&view=rss
Line Number 269, Column 102:
when viewed using Mozilla (1.7.1)

Also, trying to parse this with a SAX parser results in this:
org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x14) was found in the CDATA section.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 24/Jul/06 01:42 AM
Daniel,

Can you please look into creating a test case for this please?


Daniel Hurst - 30/Jul/06 09:20 PM
Confirmed in HEAD today. However, recent versions of Jira filter these characters out before being stored in the database. So this should only cause problems for people with legacy data.

Scott Farquhar [Atlassian] - 19/Oct/06 03:21 AM
We need to write a unit test to confirm that our xml escape code handles these characters.