Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • It does however require mapping annotations for each field. Commented Apr 14, 2011 at 5:36
  • 1
    Not true, I doesn't require. You can change default behaviour and it will use only present fields. Commented Apr 24, 2011 at 20:14
  • 1
    I heartily endorse "Simple" as well. I've used it on a couple of projects with great success. "Simple" is indeed much simpler that JAXB. Most appropriate when you have relatively simple needs: Got objects that need to be written to storage to later be re-hydrated as objects again. JAXB has far more features and flexibility, but it's an "80/20" kind of thing, most of the time in most projects you may need only the simple subset of features. Commented Jul 23, 2015 at 20:35
  • Works well if you just want a 1:1 mapping. If your classes evolve and you still need to deserialize old XML, you run into issues because both the documentation and the error messages are somewhat vague. Diagnosing the problem is usually doable, but figuring out how to fix it could take several days. Commented May 23, 2019 at 7:39