This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 150383 - [65cat] org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
Summary: [65cat] org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illega...
Status: RESOLVED WONTFIX
Alias: None
Product: webservices
Classification: Unclassified
Component: Designer (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-16 14:23 UTC by rajivderas
Modified: 2015-04-28 21:18 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 9906


Attachments
stacktrace (4.13 KB, text/plain)
2008-10-16 14:23 UTC, rajivderas
Details
stacktrace (8.51 KB, text/plain)
2008-10-16 14:27 UTC, rajivderas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rajivderas 2008-10-16 14:23:09 UTC
Build: NetBeans IDE Dev (Build 200810160201)
VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-b33
OS: Windows XP, 5.1, x86

User Comments:
GUEST: 1. Created Enterprise/EJB Module project
2. Added web service
3. Trying to add new operartion

yardus: 1. Create a new Web project - targeted to Tomcat 6
2. Create a new WebService from scratch
3. Add Operation... - "sayHello", returns java.lang.String, takes one parameter of type java.lang.String
4. Get this exception



Stacktrace: 
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified. 
        at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkQName(CoreDocumentImpl.java:2571)
        at com.sun.org.apache.xerces.internal.dom.ElementNSImpl.setName(ElementNSImpl.java:117)
        at com.sun.org.apache.xerces.internal.dom.ElementNSImpl.<init>(ElementNSImpl.java:80)
        at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.<init>(ElementImpl.java:131)
        at com.sun.xml.messaging.saaj.soap.impl.ElementFactory.createElement(ElementFactory.java:112)
        at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createElement(SOAPDocumentImpl.java:131)
Comment 1 rajivderas 2008-10-16 14:23:20 UTC
Created attachment 71975 [details]
stacktrace
Comment 2 rajivderas 2008-10-16 14:27:15 UTC
Build: NetBeans IDE Dev (Build 200810160201)
VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-b33
OS: Windows XP, 5.1, x86

User Comments: 


Stacktrace: 
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified. 
        at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkQName(CoreDocumentImpl.java:2571)
        at com.sun.org.apache.xerces.internal.dom.ElementNSImpl.setName(ElementNSImpl.java:117)
        at com.sun.org.apache.xerces.internal.dom.ElementNSImpl.<init>(ElementNSImpl.java:80)
        at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.<init>(ElementImpl.java:131)
        at com.sun.xml.messaging.saaj.soap.impl.ElementFactory.createElement(ElementFactory.java:112)
        at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createElement(SOAPDocumentImpl.java:131)
Comment 3 rajivderas 2008-10-16 14:27:24 UTC
Created attachment 71977 [details]
stacktrace
Comment 4 Jaromir Uhrik 2008-10-17 08:27:14 UTC
Reassigning - according to the stacktrace it seems to belong to websvc module. Please evaluate.
Comment 5 Ken Frank 2008-10-19 18:09:06 UTC
rajivderas

- are there any non basic ascii characters in

path to where nb is installed ?
path to userdir
name of project or path to it ?

in any file contents or file name ?


also, what locale/regional setting are you running netbeans ?

ken.frank@sun.com
Comment 6 Milan Kuchtiak 2008-11-27 15:41:17 UTC
Reporter, please, response those questions(given by KFrank), since it's difficult to reproduce the issue.
Xerces complains here about illegal character.
The best would be to attach entire project. 
May be the package name contains a strange character.
Comment 7 Milan Kuchtiak 2009-09-30 14:08:55 UTC
Closed - not enough information to reproduce.
Comment 8 bbinct 2015-04-28 20:08:38 UTC
This is marked as Wont Fix.  I'm not sure there is even a "bug"...  

But what if this exception were changed to include the offending character, perhaps the location (offset) in the file, and event better, perhaps the 10-20 characters preceding and following the character that caused the error.

I received this error in a stack trace using the Geoserver opensource product.  I'm sure there is some data in my map layer that caused the error, but I have no clues to go by.  The XML is generated and used internally by Geoserver, so I'm not even sure what it looked like... 

So I guess I'm asking if contextual information could be added in the exception text.  

Would I try to rephrase this "bug" as an enhancement request?  Or simply reference it and create a new bug report?  I'm new here...