Bug 4462 - Opening sourcewindow on funit-child org.jdom.IllegalDataException: The data " "is not legal for a JDOM character content: 0xc is not a legal XML character.
Summary: Opening sourcewindow on funit-child org.jdom.IllegalDataException: The data "...
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
: 4535 (view as bug list)
Depends on:
Blocks: 3392
  Show dependency treegraph
 
Reported: 2007-05-04 16:04 UTC by Nurdin Premji
Modified: 2007-06-21 19:24 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nurdin Premji 2007-05-04 16:04:23 UTC
org.jdom.IllegalDataException: The data "

" is not legal for a JDOM character content: 0xc is not a legal XML character.
   at org.jdom.Text.setText(FryskGui)
   at org.jdom.Text.<init>(FryskGui)
   at org.jdom.Element.setText(FryskGui)
   at frysk.dom.DOMLine.<init>(FryskGui)
   at frysk.dom.DOMImage.addSource(FryskGui)
   at frysk.dom.DOMFactory.createDOM(FryskGui)
   at frysk.gui.srcwin.SourceWindow.generateProcStackTrace(FryskGui)
   at frysk.gui.srcwin.SourceWindow.finishSourceWin(FryskGui)
   at frysk.gui.srcwin.SourceWindow$LockObserver$39.run(FryskGui)
   at org.gnu.glib.CustomEvents.runEvents(libgtkjava-2.8.so)
   at org.gnu.gtk.Gtk.gtk_main(libgtkjava-2.8.so)
   at org.gnu.gtk.Gtk.main(libgtkjava-2.8.so)
   at frysk.gui.Gui.gui(FryskGui)
   at frysk.gui.FryskGui.main(FryskGui)

Has to do with all the ^L (Form feed) characters in funit-child source code.
Comment 1 Rick Moseley 2007-06-21 19:19:08 UTC
*** Bug 4535 has been marked as a duplicate of this bug. ***
Comment 2 Rick Moseley 2007-06-21 19:24:09 UTC
I fixed the problem of the CTRL L(Form Feed) character(x0c) in the source.  I
check the line for XML validity and if a line is found invalid all of the
characters in the line are then checked and replaced with a space if an invalid
character is found.

The odd coloring got much better(about 98%+ accurate, but there is still an
issues with that not related to the form feed problem.  I will open another bug
against that issue.