Should I use JAXB now that I get warnings that it is deprecated?

Asked Oct 26 '18 at 17:08

Active Oct 26 '18 at 17:08

Viewed 34 times

I am thinking about introducing some xml serialization/deserialization library for 20 year old code which uses string appending to construct xml documents. I would like to stick to JAXB api if possible. But I get deprecated warnings in Eclipse and if I am not wrong it has been removed in Java 9. The question then is, is it gone like, poof!!! ?

That seems unlikely seeing how widely xml is used. Or is it gone because jdk has an alternative for it ? If it hasn't disappeared completely how does one use JAXB and be future proof.

I am on jdk 1.8.

asked Oct 26 '18 at 17:08

ShaggyInjun

2,880
2
31
52

1

https://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j – Ivan Oct 26 '18 at 17:17
1

Check out the accepted answer of the above SO post. – PKey Oct 26 '18 at 17:18
As JSON is pervasively used, you might consider Jackson, which supports XML as a serialization format. – chrylis -cautiouslyoptimistic- Oct 26 '18 at 17:23
Downstream expects it to be xml. So can't switch over. – ShaggyInjun Oct 26 '18 at 17:38

Should I use JAXB now that I get warnings that it is deprecated?

0 Answers0