Whay sax (jaxp) so sensestive ?

i have intresting problem ;)
my applet read a big xml files and everything is ok.
but when i have a problem for example NullPointerException in my applet the parser is crashed
how can i make that the parser will ignore from that kind of problem :)

Hi,
are you parsing a large xml file? so that the lenght of your file is bigger than the length of buffer used by the method characters()? If so the problem is related to bug 4404579. this bug is just fixed. Look for this bug an you'll find an answer to your question. Otherwise specify your question with more details.
good luck
abaman

Similar Messages

Jaxa xml tutorials, does anyone have some tutorial for using xml in java??

jaxa xml tutorials, does anyone have some tutorial for using xml in java??
can be dom,sax,jaxp whatever....
i try to find in google but din't find any complete one....

dapim wrote:
jaxa xml tutorials, does anyone have some tutorial for using xml in java??
can be dom,sax,jaxp whatever....
i try to find in google but din't find any complete one....I would imagine anyone here would just produce the same set of hits that you did, so why waste our time doing it only to direct you to the same one(s) you already found and rejected.

Design pattern for converting multiple complex Java objects to XML

What is the traditionally accepted high performance mechanism for converting Java objects to XML? Some options I have explored are:
1. SAX-JAXP
2. DOM-JAXP
3. JAXB
4. Castor
Which of these usually performs the best for large, complex objects which contain multiple subobjects?
Thanks.

Take a look at XStream. It will simplify your life considerably.
Typical code snipped
XStream xStream = new XStream();
xStream.toXML(someJavaObject);That's it. Regarding the others...
1. SAX-JAXP
Can be used for XML -> Java Objects, but you have to write significant amounts of ugly, high maintainenance code
2. DOM-JAXP
Slower and more memory intensive than SAX because you need to read the whole object into memory first. Just as ugly and high maintenance.
3. JAXB
Actually very good for going from a POJO to XML, but rubbish in the opposite direction. The worst part is it adds an extra step to your build process as you need to tell it to generate and compile the source for doing this.
4. Castor
Not used it since JAXB came out. Works pretty much in the same way but also supports XML -> POJOs.

Buiding xml file using SAX parser of JAXP

Please send me xml building using the sax parser.This is the urgent requirement ,iam not geeting how to solve this problem.so please anybody can help with one best example

You don't build an XML file with a parser. A parser reads an XML file and converts it to some internal representation. Try reading this tutorial:
http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/

Is there a way to get the actual XML string when using the JAXP SAX Parser?

Hi All,
I am using a JAXP SAX xml parser and am looking for a way to get the actual line of xml that is being parsed from within a content handler.
Here's my scenario. Consider the following example xml document.
<formCollection>
   <form name="myForm">
      <text/>
      <selection/>
   </form>
   <form name="anotherForm">
      <text/>
   </form>
</formCollection>My hope is to validate the entire document and then insert an xml string containing each "form" element (and its sub-elements) into a map for later use. My thought was to create a String as each "form" element is being parsed (begining with the form's startElement event and concatenating until the form's endElement event is reached) and then inserting this string into the map. Is there a way to get the actual line of xml that is being parsed, rather than just the element name and attribute values?

DrClap wrote:
YouRang wrote:
2. The first handler would validate the entire XML document, extract the "type" attribute from each <form> element, and place each <form> element and its sub-elements into the map of Strings, using the "type" attribute as the key. The second handler would take a <form> element and parse it into a Form object for the display. This option was the impetus for my question because it relies on the first handler being able to access the entire <form> element XML String and write it to a map.I don't see why you need the raw data from the XML document here. You should already be abstracting your data into Java classes in the first handler, instead of making the second handler do the parsing all over again.Correct, I am not referring to XForms. In this case, it happens that I am using the XML to generate an SWT ScrolledForm object and, thus, the XML element name happens to be named "form." However, the concept/design problem could apply to any type of object and the XML element could be appropriately renamed.
My experience with XSLT is limited and I haven't done anything with it for several years. With that said, it seems that it is primarily used for generating web content, which wouldn't apply in this case because this is for a client-server application. I could be off base on this one -- if XSLT applies to much broader translations and would be more appropriate for generating Java objects than my current methodology, I could certainly look into it further.
I apologize that option two didn't make more sense; it is difficult to explain. Yes, optimally the data should be abstracted into Java classes in the first handler. This is really an elaboration that I failed to specify when explaining option one. The problem is that the user can choose to create any number of "forms" of any type. For instance, let's say that from the File -> New menu there are options for seven different types of forms and each form is used to send completely different data. The user can select form1, select form1 again, select form4, and select form7 (or any other combination) and bring up tabs that display the different forms. The user can then enter data and submit each form separately. When the user selects File -> New -> FormX, a SWT ScrolledForm object that corresponds with FormX must be given to the display. Because SWT ScrolledForm objects do not allow a deep copy, I cannot simply read the XML <form> elements at initialization, parse them into ScrolledForm objects, and pass deep copies of the ScrolledForm objects to the display each time the user clicks File -> New -> FormX. The only simple way I see of getting a new copy of a ScrolledForm object is to reparse the appropriate XML <form> element in order to create one each time the user selects File -> New -> FormX. As such, one handler would need to read the entire XML document and parse the <form> elements into a map (or some other data structure) and another handler would need to parse individual <form> elements into SWT ScrolledForm objects. The first handler would be called at initialization and the second handler would be called each time a user clicked on File -> New -> FormX. Once again, this isn't exactly my favorite implementation... but seems the simplest given that there is no way to do a deep copy of an SWT ScrolledForm object. Hopefully that makes a little more sense. No worries if it doesn't -- I just figured I'd throw this out there and see if anyone had a better idea.

Validating xml file against a specific schema using jaxp sax parser

Hi,
I would like to validate a soap xml given below
<?xml version="1.0" encoding="UTF-8"?>
<Envelope>
     <Body>
          <name>pavan</name>
          <number>123</number>
     </Body>
</Envelope>
to validate against the schema of soap from url "http://www.w3.org/2003/05/soap-envelope". I dont want to have this namespace in the xml. How can I validate against the specified schema using jaxp sax parser?
Please help.
Thanks,
T.Pavan kumar

Any one, please help.

SAX problem with jaxp

Hi all
I tried the JAXP but I have this error: could anyone help? Thanks a lot (my java code is under the error)
Thanks
Cecile
Exception in thread "main" org.xml.sax.SAXParseException: org.apache.crimson.parser/P-076 Malformed UTF-8 char -- is an
XML encoding declaration missing?
at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1038)
at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1010)
at org.apache.crimson.parser.InputEntity.peek(InputEntity.java, Compiled Code)
at org.apache.crimson.parser.Parser2.peek(Parser2.java:2927)
at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:999)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java, Compiled Code)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:232)
at sivpn.ChargementSAX.main(ChargementSAX.java:521)
SAXParserFactory factory = SAXParserFactory.newInstance();
factory.setValidating(true);
SAXParser saxParser = factory.newSAXParser();
saxParser.parse("toto.xml", handler );

The error is in your XML input, not in your Java code. Probably the XML doesn't declare its encoding, so the parser assumes that it is encoded in UTF-8. And probably it contains some character (like an accented letter, for example) that is not part of the UTF-8 encoding. So contact the person who created the XML -- which is not well-formed XML, by the way -- and get them to fix it. It's possible that declaring the encoding as ISO8859-1 might work, but it might not. All depends on what the invalid character is.

Jaxp underlying sax class question

Below is a class that uses the JAXP layer and parses a xml document. All works fine and my results are proper. I would like to use the JAXP abstraction in some code at work, but I am not sure of two things.
1) What underlying parser does this use.? I believe the answser has to do with where the class was downloaded? Crimson from sun, Xerces from Apache. But I am writing code that will go to a remote server.
2) So if the above is true, how can I through code find out what underlying parser it is using, and can I override it somehow on this remote server?
Thanks,
Scott
from java and xml oreilly
package javaxml2;
import java.io.File;
import java.io.IOException;
import java.io.OutputStreamWriter;
import java.io.Writer;
// JAXP
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParserFactory;
import javax.xml.parsers.SAXParser;
// SAX
import org.xml.sax.AttributeList;
import org.xml.sax.HandlerBase;
import org.xml.sax.SAXException;
* <p>
* <code>TestSAXParsing</code> is a simple class that demonstrates
* how JAXP can be used to work with SAX (the Simple API for XML).
* </p>
public class TestSAXParsing {
* <p>Provide a static entry point.</p>
public static void main(String[] args) {
try {
if (args.length != 1) {
System.err.println ("Usage: java TestSAXParsing [filename]");
System.exit (1);
// Get SAX Parser Factory
SAXParserFactory factory = SAXParserFactory.newInstance();
// Turn on validation, and turn off namespaces
factory.setValidating(true);
factory.setNamespaceAware(false);
SAXParser parser = factory.newSAXParser();
parser.parse(new File(args[0]), new MyHandler());
} catch (ParserConfigurationException e) {
System.out.println("The underlying parser does not support the requested features.");
} catch (FactoryConfigurationError e) {
System.out.println("Error occurred obtaining SAX Parser Factory.");
} catch (Exception e) {
e.printStackTrace();
class MyHandler extends HandlerBase {
private Writer out;
public MyHandler() throws SAXException {
try {
out = new OutputStreamWriter(System.out, "UTF8");
} catch (IOException e) {
throw new SAXException("Error getting output handle.", e);
public void startDocument() throws SAXException {
print("<?xml version=\"1.0\"?>\n");
public void startElement(String elementName, AttributeList atts)
throws SAXException {
print("<" + elementName);
if (atts != null) {
for (int i=0, len = atts.getLength(); i<len; i++) {
print(" " + atts.getName(i) +
"=\"" + atts.getValue(i) + "\"");
print(">");
public void endElement(String elementName) throws SAXException {
print("</" + elementName + ">\n");
public void characters(char[] ch, int start, int len) throws SAXException {
print(new String(ch, start, len));
private void print(String s) throws SAXException {
try {
out.write(s);
out.flush();
} catch (IOException e) {
throw new SAXException("IO Error Occurred.", e);

I see that there are a number of code snippets on that page, for clarity I meant this one in particular. It checks for just about every parser known before calling default. Sorry for confusion. You wouldn't have to check for this many parsers, but I sometimes take Xerces if it is there over the default.
XMLReader parser;
try { // Xerces
    parser = XMLReaderFactory.createXMLReader(
     "org.apache.xerces.parsers.SAXParser"
catch (SAXException e1) {
    try { // Crimson
      parser = XMLReaderFactory.createXMLReader(
       "org.apache.crimson.parser.XMLReaderImpl"
    catch (SAXException e2) {
      try { // ?lfred
        parser = XMLReaderFactory.createXMLReader(
         "gnu.xml.aelfred2.XmlReader"
      catch (SAXException e3) {
        try { // Piccolo
          parser = XMLReaderFactory.createXMLReader(
            "com.bluecast.xml.Piccolo"
        catch (SAXException e4) {
          try { // Oracle
            parser = XMLReaderFactory.createXMLReader(
              "oracle.xml.parser.v2.SAXParser"
          catch (SAXException e5) {
            try { // default
              parser = XMLReaderFactory.createXMLReader();
            catch (SAXException e6) {
              throw new NoClassDefFoundError(
                "No SAX parser is available");
                // or whatever exception your method is
                // declared to throw
}

Having problem compiling JAXP - SAX example

I am new to this technology. I am trying to run all the examples which are in JWSDP1.1. Can anybody tell How to solve the following error.
C:\jwsdp-1.1\docs\tutorial\examples\jaxp\sax\samples>javac Echo01.java
Echo01.java:74: cannot resolve symbol
symbol : method parse (java.io.File,org.xml.sax.helpers.DefaultHandler)
location: class javax.xml.parsers.SAXParser
saxParser.parse( new File(argv[0]), handler);
^
1 error

In the command line include these files:
sax.jar
jaxp-api.jar
I mean like this :
javac -classpath ......\sax.jar;.....\jaxp-api.jar Echo01.java

Approach on parsing an XML file (JAXP, JAXB, DOM, SAX, XSLT)

I have a pretty basic xml file that contains a database table name, fields, and sort order. My job is to read the XML file, construct the query based on the information in the nodes, and then output it in various ways. I know I can use JAXP, JAXB, DOM, SAX, and XSLT for this.
I have the experience doing this using DOM. I have read up on JAXP, JAXB, and XSLT. I'm having a little bit of a difficult time on chosing the most appropriate way to do this. Again, I've always done it using DOM, but I'm not so sure that is the best way to do it here. Just looking for some recommendations from people whom are more familiar with XML parsing and processing.

markwagoner wrote:
I tried several of those but found them rather tedious. Now I just use JDOM for everything, it make life much easier.It doesn't, actually. It kept your learning curve shallow, but that's all. If you were to invest some time in JAXB, you'd find it made life easier for some things. If you invested time in XSLT, it would make life easier. Endlessly working with JDOM is incredibly tiresome after a while. You just don't know it because you never invested enough in learning anything else.
Don't bother posting any code to "enlighten" me as to how simple JDOM is. I've been using it for years.

JAXB , JAXP and SAX compare

Hi,
I want to convert XML to another XML using XML Schema.
I have XML Schema for the one I will convert to.
I also need to modify some of the data.
But I am confuse which process should I use, JAXB, JAXP or SAX.
Any suggestions?
Thanks,

javax.xml.transform

"Right" way to mix SAX and DOM in app

I'm writing a standalone desktop application that reads and stores data as XML files. Eventually, it might be converted to use some web services, but it's not a priority right now.
What I need to do is to use an XML file, which could be large, as kind of a database -- there are many entries, each with a unique identifier, and the application will query the file to find those it needs to match and returns those as objects I'm mapping.
At the moment, because this is a personal project and I'm using it to learn more technologies, I'm trying to (somewhat artificially) restrict myself to the pure Sun APIs. So far, my investigations have pointed to JAXP (by including Java EE 5 libraries) with StAX (including JAX-WS). Which raises two questions:
1) To do this "right", do I really need to bundle my app with the entire JaveEE+Metro stack?
2) Is there a better solution than StAX that's fully Java 5 compliant, even if it means stepping out of the Sun box? I haven't found many references to other solutions that are more recent than 2004. Is parsing XML on an app that has nothing to do with an appserver that uncommon?

More likely than not, I won't be abstracting to that degree. If the current structure isn't right, I'd update the app instead of storing that kind of information in more files.
I imagine at this point an example would be more effective. The app is itself more of an inventory browser that can jump around different searches dynamically. As an illustration, imagine that it's an inventory for DVDs. One central file will be your collection (with each entry containing a movie ID, date of purchase, etc). Another file would be more static, a list of DVDs themselves. These entries would contain information about the package itself -- how many discs? What's the title of the package? Which special features does it have? It would also point to an entry in yet another file which would have information about the film, containing biographies of the people listed under the movie credits.
Basically, I want a flatfile database that I can do joins on that are split up into different files. There are few files (here, one) that will be constantly updated by the user. The others could be modified if needed, but it's not going to be optimized for it. (For example, you could own a DVD that nobody's ever heard of, and put in the info yourself.) Periodically, one or more of the more static files is updated and will be downloaded into the app.
One of the advantages I see for this is that, in the future, I could with few changes turn this into more of a web service. Instead of pushing changes in those few files, the app would look to a web service for the data it would now find in files on the user's hard drive. But for now, it also has to be one standalone package.
To answer the question, the file that will most commonly be updated by the user is the one that I don't have problems loading into memory in full. It's the other data that it links to which I want to be able to search and load into objects dynamically. My current implementation is to run the file through SAX and grab the data as it sees it, but it's really ugly. That could very well be how I'm using it and not because I'm trying to shoehorn some functionality into a technique it doesn't fit, but I'd like to find that out. ;)

Error while Validating xml against a schema using jaxp

Hi All,
Following code validates xml against a schema using JAXP .It gives SAXNotRecognizedException error when you run the program.
static final String JAXP_SCHEMA_LANGUAGE = "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
static final String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";
SAXParserFactory myFactory = SAXParserFactory.newInstance();
myFactory.setNamespaceAware(true);
myFactory.setValidating(true);
javax.xml.parsers.SAXParser parser;
String filename = "C:/Note.xml";
File xmlFile = new File(filename);
try
     DefaultHandler handler = new DefaultHandler();
     parser = myFactory.newSAXParser();
     parser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
     parser.parse(xmlFile, handler);
catch (ParserConfigurationException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
catch (SAXException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
catch (IOException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
Error Details :
org.xml.sax.SAXNotRecognizedException: http://java.sun.com/xml/jaxp/properties/schemaLanguage
     at org.apache.xerces.framework.XMLParser.setProperty(XMLParser.java:1682)
     at org.apache.xerces.parsers.SAXParser.setProperty(SAXParser.java:770)
     at org.apache.xerces.jaxp.SAXParserImpl.setProperty(SAXParserImpl.java:183)
How do i fix the above mentioned problem ?
Thanks in Advance.
Ansh

Validate with the JAXP DOMParser instead of the JAXP SAXParser.
To validate with a SAXParser use the xerces SAXParser.
thanks,
Deepak

Xml sax parser

Hi all,
I am newbie to xml. I am using SAX parser for parsing xml documents. I have to write a code which parses all types of xsd files(including which can contain inline , referenced or both). Can anyone help / guide me how to code a generic xsd parser??
Thanks in advance,

An XSD file is an XML file, so you can parse it using sax.
See :
http://java.sun.com/webservices/jaxp/dist/1.1/docs/tutorial/sax/2a_echo.html
http://java.sun.com/webservices/jaxp/dist/1.1/docs/tutorial/sax/work/Echo02.java
See also:
http://www.oracle.com/technology/tech/xml/xdk/doc/production/java/doc/java/javadoc/oracle/xml/parser/schema/XMLSchema.html#getXMLSchemaNodeTable

Org.xml.sax error content not allowed in prolog

Hi,
I am running Jetty 6.x on SUSE and there is a webapp called pyjasper i am trying to run on it. the context maps fine and it displays the content however, when i use the applet in the webapp to create a report (.jasper) it gives me a org.xml.sax Parse exception: content not allowed in prolog.
A little part of the error is pasted below:
generating report /tmp/pyJasper/compiled-reports/6390c37d0ea810c7fae3e647c2f86817.jasper
Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.commons.digester.Digester.parse(Digester.java:1647)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:239)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:226)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:214)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
2010-03-04 09:15:59.073::WARN: /pyJasper/jasper.py
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:243)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:226)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:214)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
I am guessing this is some sort of an error in xml parsing. I found couple of solutions on sun java forums but none of them worked for me. Right now I am trying to figure out whether this is being caused by the applet or the java itself.
Apparently other people who use this applet do not have a problem and they have the exact same files as me. So I am not sure what exactly is causing tihs problem. Bit of a noob.
Any help would be greatly appreciated.
THANK YOU VERY MUCH!!!! :)

Hi thanks you very much for the reply.
In my message I forgot to mention that I edited my prologs to "<?xml version = "1.0" encoding = "UTF-8"?>" and the jetty.xml that has the server configuration has:
<?xml version = "1.0" encoding = "UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
I apologize for the clarity of my message. I meant to say that I was wondering whether the problem is with the xm files that java has, or the xml files that are in the pyjasper package that I downloaded?
I also checked for byte order mark using hex editor to see if those six characters were in front of my xml files. None of the files in the pyjasper package had the BOM so that solution did not work.
Is there something wrong with the above xml prolog?
I have been reading tons of different posts and stuf trying to figure this out for the past month but juts cannot seem to get it to work.
Thanks.

Whay sax (jaxp) so sensestive ?

Similar Messages

Maybe you are looking for