Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Bug in parser?

Bug in parser?

2003-05-30       - By Jon Wilmoth
Reply:     1     2     3     4     5     6     7  

Ah.  I thought
getClass().getResourceAsStream("test.xml") delegated
to the
getClass().getClassLoader().getResourceAsStream("test.xml")

and it was the location of the file (i.e.
com/acme/app/text.xml) that specified the package to
look under not the invoking class.

--- Jacob Kjome <hoju@(protected)> wrote:
>
> I can tell you exactly why it didn't find
> it.  getClass().getResourceAsStream("test.xml")
> looks for the test.xml file
> in the same package as your class exists and nowhere
> else.  If you want to
> find test.xml in the root of the classpath, then do
> either
> getClass().getResourceAsStream("/test.xml") or
>
getClass().getClassLoader().getResourceAsStream("test.xml")
>
> Jake
>
> At 01:46 PM 5/29/2003 -0700, you wrote:
> >Thank you that was the issue.  Although I'm not
> sure
> >why getClass().getResourceAsStream(testDoc); was
> not
> >able to find a file that was present in the
> >/WEB-INF/classes directory!  Changing the servlet
> >initialization code to
> >context.getResourceAsStream("/WEB-INF/classes/" +
> >testDoc); worked!
> >
> >Thanks again,
> >Jon
> >
> >--- Michael Rafael Glavassevich
> ><mrglavas@(protected)> wrote:
> > > Hi Jon,
> > >
> > > You might want to check if you're passing in a
> > > non-null InputStream. I
> > > believe getResourceAsStream (unless your class
> was
> > > loaded by some custom
> > > ClassLoader), searches the classpath for the
> > > resource you want, so if
> > > you've only have jars in your classpath, I doubt
> it
> > > would search in the
> > > file system.
> > >
> > > -----------------------------------------
> > > Michael Glavassevich
> > > mrglavas@(protected)
> > > Candidate for Bachelor of Applied Science
> > > Computer Engineering
> > > University of Waterloo
> > >
> > > On Tue, 27 May 2003, Jon Wilmoth wrote:
> > >
> > > > I've tried simplifying the test by attempting
> to
> > > parse
> > > > a document without a dtd reference.
> > > >
> > > > <?xml version="1.0"?>
> > > > <test>sample</test>
> > > >
> > > > The java code I use, which still results in an
> > > > exception is:
> > > >
> > > > log.debug("TRYING TO PARSE SIMPLE
> DOCUMENT...");
> > > > SAXBuilder builder = new SAXBuilder(false);
> > > >
> builder.setIgnoringElementContentWhitespace(true);
> > > >
> > >
>
>builder.setFeature("http://xml.org/sax/features/validation",
> > > > false);
> > > >
> > > > String testDoc = "test.xml";
> > > > try {
> > > >     Document doc =
> > > >
> > >
>
>builder.build(getClass().getResourceAsStream(testDoc));
> > > >
> > > >     //I never get here!
> > > >     log.debug("Successfully parsed test
> > > document!");
> > > >
> > > > } catch (JDOMException jdome) {
> > > >     Throwable root = jdome.getCause();
> > > >     if (root != null) {
> > > >         log.error("Root cause:" +
> > > root.getMessage());
> > > >     }
> > > >     log.error("Failed to parse " + testDoc + "
> > > file",
> > > > root);
> > > > }
> > > >
> > > >
> > > > --- Michael Rafael Glavassevich
> > > > <mrglavas@(protected)> wrote:
> > > > > Hi Jon,
> > > > >
> > > > > It would be great if you posted a snippet of
> > > code
> > > > > before and including
> > > > > the invocation of SAXBuilder.build, in order
> to
> > > > > diagnose your problem. It
> > > > > seems that there is something wrong with the
> > > > > location specified for your
> > > > > XML file (either an invalid URI, or
> java.net.URL
> > > > > doesn't recognize the
> > > > > protocol/scheme of the URI). In either case,
> > > Xerces
> > > > > is unable to read
> > > > > your file.
> > > > >
> > > > > As a separate issue, I noticed that the
> system
> > > ID
> > > > > that you specified for
> > > > > your DTD is not a valid URI. It should be
> > > > >
> > >
> "file:///C:/temp/projects/EventRegistrations.dtd"
> > > > > instead of
> > > > >
> > >
> "file:///C:\temp\projects\EventRegistrations.dtd"
> > > > > ('\' isn't a valid URI
> > > > > character). Xerces (by default) will fix up
> the
> > > > > system ID before it's
> > > > > used. However, if you want your documents to
> be
> > > > > portable across different
> > > > > XML parsers, then you need to make sure that
> > > URIs
> > > > > you specify actually
> > > > > meet the URI spec.
> > > > >
> > > > > Hope that helps.
> > > > >
> > > > > -----------------------------------------
> > > > > Michael Glavassevich
> > > > > mrglavas@(protected)
> > > > > Candidate for Bachelor of Applied Science
> > > > > Computer Engineering
> > > > > University of Waterloo
> > > > >
> > > > > On Sat, 24 May 2003, Jon Wilmoth wrote:
> > > > >
> > > > > > I'm trying to parse a very simple xml
> document
> > > > > with
> > > > > > xerces 2.4.0.  Unfortunately I get the
> > > following
> > > > > > error:
> > > > > >
> > > > > > java.net.MalformedURLException
> > > > > >         at
> java.net.URL.<init>(URL.java:613)
> > > > > >         at
> java.net.URL.<init>(URL.java:476)
> > > > > >         at
> java.net.URL.<init>(URL.java:425)
> > > > > >         at
> > > > > >
> > > > >
> > > >
> > >
>
>org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > > > >
> > > >
> > >
>
>org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > > > >
> > > >
> > >
>
>org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > > > >
> > > >
> > >
>
>org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > >
> org.apache.xerces.parsers.XMLParser.parse(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > > > >
> > > >
> > >
>
>org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> > > > > > Source)
> > > > > >         at
> > > > > >
> > > > >
> > >
> org.jdom.input.SAXBuilder.build(SAXBuilder.java:354)
> > > > > >         at
> > > > > >
> > > > >
> > >
> org.jdom.input.SAXBuilder.build(SAXBuilder.java:673)
> > > > > >
> > > > > > The document:
> > > > > > <?xml version="1.0"?>
> > > > > > <!DOCTYPE EventRegistrations SYSTEM
> > > > > >
> > >
> "file:///C:\temp\projects\EventRegistrations.dtd">
> > > > > > <EventRegistrations>
> > > > > >         <event
> > > > >
> name="test.events.BusinessObjectChangeEvent">
> > > > > >
> > > <listener>test.ObjectCreationListener</listener>
> > > > > >         </event>
> > > > > > </EventRegistrations>
> > > > > >
> > > > > > Passes validation in my xml editor.
> What's
> > > going
> > > > > on?
> > > > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > http://search.yahoo.com
> > > >
> > > >
> > >
>
>---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > xerces-j-user-unsubscribe@(protected)
> > > > For additional commands, e-mail:
> > > xerces-j-user-help@(protected)
> > > >
> > >
> > >
>
>---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > xerces-j-user-unsubscribe@(protected)
> > > For additional commands, e-mail:
> > > xerces-j-user-help@(protected)
> > >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Yahoo! Calendar - Free online calendar with sync to
> Outlook(TM).
> >http://calendar.yahoo.com
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> xerces-j-user-unsubscribe@(protected)
> >For additional commands, e-mail:
> xerces-j-user-help@(protected)
>


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)