Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350529 - [Java][Java-KDM] An invalid XML character (Unicode: 0x2) was found in the element content
Summary: [Java][Java-KDM] An invalid XML character (Unicode: 0x2) was found in the ele...
Status: NEW
Alias: None
Product: MoDisco
Classification: Modeling
Component: Technologies (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-28 04:55 EDT by Dmitry Smirnov CLA
Modified: 2011-09-28 16:28 EDT (History)
1 user (show)

See Also:

Attachments
Sample file that cause an exception (234 bytes, application/octet-stream)
2011-06-28 04:58 EDT, Dmitry Smirnov 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 Dmitry Smirnov CLA 2011-06-28 04:55:39 EDT 
Build Identifier: I20110613-1736

An exception occurs while saving discovered KDM model if Java source file contains non-printable symbol.

Attached is the example of such a file.
The line of code contains a string literal which is a symbol for 0x2 hex code. Java Editor shows it as a small empty rectangle, Java compiler does not warn or produce an error.

Reproducible: Always

Steps to Reproduce:
1. Create a Java project
2. Add an attached file to a project
3. Run Discovery->Discoverers->KDM Code model from Java project
Comment 1 Dmitry Smirnov CLA 2011-06-28 04:58:11 EDT 
Created attachment 198709 [details]
Sample file that cause an exception
Comment 2 Gregoire Dupe CLA 2011-09-28 10:46:30 EDT 
Hello,

I'm really sorry, but the year we have to focus on the move to EMF Facet. We may not be able to work on this bug. That's why cannot plan this bug for the Juno release.

Regards,
Gregoire Dupe