Best XML parser for Java

Question

I need to read smallish  few MB at the most  UTF-8 encoded  XML files  rummage around looking at various elements and attributes  perhaps modify a few and write the XML back out again to disk  preferably with nice  indented formatting    What would be the best XML parser for my needs   There are lots to choose from   Some I m aware of are    JDOM Woodstox XOM dom4j VTD-XML Xerces-J Crimson   And of course the one in the JDK  I m using Java 6    I m familiar with Xerces but find it clunky   Recommendations

User · Answer

I have found dom4j to be the tool for working with XML  Especially compared to Xerces

User · Answer

I have found dom4j to be the tool for working with XML  Especially compared to Xerces

User · Answer

If speed and memory is no problem  dom4j is a really good option  If you need speed  using a StAX parser like Woodstox is the right way  but you have to write more code to get things done and you have to get used to process XML in streams

User · Answer

Simple XML http   simple sourceforge net  is very easy for  de serializing objects

User · Answer

In addition to SAX and DOM there is STaX parsing available using XMLStreamReader which is an xml pull parser

User · Answer

I think you should not consider any specific parser implementation  Java API for XML Processing lets you use any conforming parser implementation in a standard way  The code should be much more portable  and when you realise that a specific parser has grown too old  you can replace it with another without changing a line of your code  if you do it correctly    Basically there are three ways of handling XML in a standard way       SAX This is the simplest API  You read the XML by defining a Handler class that receives the data inside elements attributes when the XML gets processed in a serial way  It is faster and simpler if you only plan to read some attributes elements and or write some values back  your case   DOM This method creates an object tree which lets you modify access it randomly so it is better for complex XML manipulation and handling  StAX This is in the middle of the path between SAX and DOM  You just write code to pull the data from the parser you are interested in when it is processed    Forget about proprietary APIs such as JDOM or Apache ones  i e  Apache Xerces XMLSerializer  because will tie you to a specific implementation that can evolve in time or lose backwards compatibility  which will make you change your code in the future when you want to upgrade to a new version of JDOM or whatever parser you use  If you stick to Java standard API  using factories and interfaces  your code will be much more modular and maintainable   There is no need to say that all  I haven t checked all  but I m almost sure  of the parsers proposed comply with a JAXP implementation so technically you can use all  no matter which

User · Answer

I think you should not consider any specific parser implementation  Java API for XML Processing lets you use any conforming parser implementation in a standard way  The code should be much more portable  and when you realise that a specific parser has grown too old  you can replace it with another without changing a line of your code  if you do it correctly    Basically there are three ways of handling XML in a standard way       SAX This is the simplest API  You read the XML by defining a Handler class that receives the data inside elements attributes when the XML gets processed in a serial way  It is faster and simpler if you only plan to read some attributes elements and or write some values back  your case   DOM This method creates an object tree which lets you modify access it randomly so it is better for complex XML manipulation and handling  StAX This is in the middle of the path between SAX and DOM  You just write code to pull the data from the parser you are interested in when it is processed    Forget about proprietary APIs such as JDOM or Apache ones  i e  Apache Xerces XMLSerializer  because will tie you to a specific implementation that can evolve in time or lose backwards compatibility  which will make you change your code in the future when you want to upgrade to a new version of JDOM or whatever parser you use  If you stick to Java standard API  using factories and interfaces  your code will be much more modular and maintainable   There is no need to say that all  I haven t checked all  but I m almost sure  of the parsers proposed comply with a JAXP implementation so technically you can use all  no matter which

User · Answer

I have found dom4j to be the tool for working with XML  Especially compared to Xerces

User · Answer

I have found dom4j to be the tool for working with XML  Especially compared to Xerces

User · Answer

If speed and memory is no problem  dom4j is a really good option  If you need speed  using a StAX parser like Woodstox is the right way  but you have to write more code to get things done and you have to get used to process XML in streams

User · Answer

If speed and memory is no problem  dom4j is a really good option  If you need speed  using a StAX parser like Woodstox is the right way  but you have to write more code to get things done and you have to get used to process XML in streams

User · Answer

Simple XML http   simple sourceforge net  is very easy for  de serializing objects

User · Answer

If speed and memory is no problem  dom4j is a really good option  If you need speed  using a StAX parser like Woodstox is the right way  but you have to write more code to get things done and you have to get used to process XML in streams

User · Answer

I wouldn t recommended this is you ve got a lot of  thinking  in your app  but using XSLT could be better  and potentially faster with XSLT-to-bytecode compilation  than Java manipulation

User · Answer

Here is a nice comparision on DOM  SAX  StAX  amp  TrAX   Source  http   download oracle com docs cd E17802 01 webservices webservices docs 1 6 tutorial doc SJSXP2 html       Feature  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  StAX  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp      SAX  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp     DOM  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp     TrAX     API Type nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Pull streaming  nbsp  nbsp  nbsp   Push streaming    nbsp  nbsp  nbsp In memory tree   nbsp  nbsp  nbsp XSLT Rule  Ease of Use nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   High  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Medium  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   High  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Medium    XPath Capability nbsp  nbsp   No nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp    nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp    nbsp  nbsp  nbsp  nbsp Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   nbsp  nbsp Yes    CPU  amp  Memory  nbsp  nbsp  nbsp  Good  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Good  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Varies  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Varies    Forward Only  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No    Read XML  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes    Write XML  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes    CRUD  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No

User · Answer

Here is a nice comparision on DOM  SAX  StAX  amp  TrAX   Source  http   download oracle com docs cd E17802 01 webservices webservices docs 1 6 tutorial doc SJSXP2 html       Feature  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  StAX  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp      SAX  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp     DOM  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp     TrAX     API Type nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Pull streaming  nbsp  nbsp  nbsp   Push streaming    nbsp  nbsp  nbsp In memory tree   nbsp  nbsp  nbsp XSLT Rule  Ease of Use nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   High  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Medium  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   High  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Medium    XPath Capability nbsp  nbsp   No nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp    nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp    nbsp  nbsp  nbsp  nbsp Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   nbsp  nbsp Yes    CPU  amp  Memory  nbsp  nbsp  nbsp  Good  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Good  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Varies  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Varies    Forward Only  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No    Read XML  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes    Write XML  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes    CRUD  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp   No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  Yes  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  nbsp  No

User · Answer

In addition to SAX and DOM there is STaX parsing available using XMLStreamReader which is an xml pull parser

User · Answer

I wouldn t recommended this is you ve got a lot of  thinking  in your app  but using XSLT could be better  and potentially faster with XSLT-to-bytecode compilation  than Java manipulation

User · Answer

I think you should not consider any specific parser implementation  Java API for XML Processing lets you use any conforming parser implementation in a standard way  The code should be much more portable  and when you realise that a specific parser has grown too old  you can replace it with another without changing a line of your code  if you do it correctly    Basically there are three ways of handling XML in a standard way       SAX This is the simplest API  You read the XML by defining a Handler class that receives the data inside elements attributes when the XML gets processed in a serial way  It is faster and simpler if you only plan to read some attributes elements and or write some values back  your case   DOM This method creates an object tree which lets you modify access it randomly so it is better for complex XML manipulation and handling  StAX This is in the middle of the path between SAX and DOM  You just write code to pull the data from the parser you are interested in when it is processed    Forget about proprietary APIs such as JDOM or Apache ones  i e  Apache Xerces XMLSerializer  because will tie you to a specific implementation that can evolve in time or lose backwards compatibility  which will make you change your code in the future when you want to upgrade to a new version of JDOM or whatever parser you use  If you stick to Java standard API  using factories and interfaces  your code will be much more modular and maintainable   There is no need to say that all  I haven t checked all  but I m almost sure  of the parsers proposed comply with a JAXP implementation so technically you can use all  no matter which

User · Answer

I think you should not consider any specific parser implementation  Java API for XML Processing lets you use any conforming parser implementation in a standard way  The code should be much more portable  and when you realise that a specific parser has grown too old  you can replace it with another without changing a line of your code  if you do it correctly    Basically there are three ways of handling XML in a standard way       SAX This is the simplest API  You read the XML by defining a Handler class that receives the data inside elements attributes when the XML gets processed in a serial way  It is faster and simpler if you only plan to read some attributes elements and or write some values back  your case   DOM This method creates an object tree which lets you modify access it randomly so it is better for complex XML manipulation and handling  StAX This is in the middle of the path between SAX and DOM  You just write code to pull the data from the parser you are interested in when it is processed    Forget about proprietary APIs such as JDOM or Apache ones  i e  Apache Xerces XMLSerializer  because will tie you to a specific implementation that can evolve in time or lose backwards compatibility  which will make you change your code in the future when you want to upgrade to a new version of JDOM or whatever parser you use  If you stick to Java standard API  using factories and interfaces  your code will be much more modular and maintainable   There is no need to say that all  I haven t checked all  but I m almost sure  of the parsers proposed comply with a JAXP implementation so technically you can use all  no matter which

User · Answer

In addition to SAX and DOM there is STaX parsing available using XMLStreamReader which is an xml pull parser

User · Answer

If you care less about performance  I m a big fan of Apache Digester  since it essentially lets you map directly from XML to Java Beans   Otherwise  you have to first parse  and then construct your objects

User · Answer

I wouldn t recommended this is you ve got a lot of  thinking  in your app  but using XSLT could be better  and potentially faster with XSLT-to-bytecode compilation  than Java manipulation

User · Answer

In addition to SAX and DOM there is STaX parsing available using XMLStreamReader which is an xml pull parser

User · Answer

If you care less about performance  I m a big fan of Apache Digester  since it essentially lets you map directly from XML to Java Beans   Otherwise  you have to first parse  and then construct your objects

User · Answer

If you care less about performance  I m a big fan of Apache Digester  since it essentially lets you map directly from XML to Java Beans   Otherwise  you have to first parse  and then construct your objects

User · Answer

I wouldn t recommended this is you ve got a lot of  thinking  in your app  but using XSLT could be better  and potentially faster with XSLT-to-bytecode compilation  than Java manipulation

User · Answer

If you care less about performance  I m a big fan of Apache Digester  since it essentially lets you map directly from XML to Java Beans   Otherwise  you have to first parse  and then construct your objects

[java] Best XML parser for Java

Examples related to java

Examples related to xml

Examples related to parsing