Hi,
I am considering XStream and JAXB for binding my app conf files to XML.
Is there advantage to using XML Schema based solution such as when using JAXB to a solution like XStream where XML Schema is not needed?
Printable View
Hi,
I am considering XStream and JAXB for binding my app conf files to XML.
Is there advantage to using XML Schema based solution such as when using JAXB to a solution like XStream where XML Schema is not needed?
All depends on your needs. I'm using JiBX. It is very fast. You can find performance comparison in Google.
I've heard that there is a potential advantage in that the schema information can help turn the xml data into objects allowing for much greater loosening of coupling. I'm no expert in this though, far from it.
I need it for configuration files.Quote:
Originally Posted by devunion
So performance are not an issue.
And generally (at least according to the xstream FAQ) using Schema is faster.
I also think that binding is mostly used in the part of the program that performance are not an issue at - doing otherwise seem a design flaw.
My question remains:
Is there advantage to using XML Schema based solutions over solutions where XML Schema is not needed?
Maybe the intension was to binding vs the old way of doing configuration where the class was coupled with the code to write it down to disk.Quote:
Originally Posted by Fubarable