Have JiBX unmarshal using configured encoding

[sslavic]

Before this change JibxMarshaller did not use configured encoding when
unmarshalling XML. This caused issues when content being unmarshalled
was not encoded using default encoding.

This change fixes the issue by passing configured encoding to JiBX so
it gets used when unmarshalling instead of the default encoding.

Issue: SPR-7865

I have signed and agree to the terms of SpringSource Individual Contributor License Agreement.

[cbeams]

Thanks, Stevo. @poutsma, could you give a +1 on this? I'll do the merge, just want to make sure you've had a look first.

[poutsma]

Looks good to me!

[cbeams]

Merged. Stevo, there were several changes that I made along the way:

• Updated Apache license headers
• Cleaned up new whitespace (trailing whitespace in newly-added empty lines)
• Cleaned up old whitespace (FlightType had inconsistent mix of spaces vs. tabs)
• Minor changes to the commit comment (subject line sentence structure, add articles where missing in body)

Each of these are detailed in the contributor guidelines.

Thanks!

[cbeams]

See commit d2251a1, which reverts JibxUnmarshallerTests to Latin-1 instead of UTF-8. This was causing test failures on at least some systems.

[poutsma]

Indeed. Please make sure Java source files are in Latin-1 (ISO-8559-1) in future pull requests, not UTF-8. When in doubt, simply run the native2ascii tool that comes with the JDK over the source files. Quoting from the native2ascii man page:

The Java compiler and other Java tools can only process files that contain Latin-1 or Unicode-encoded (\udddd notation) characters. native2ascii converts files that contain other character encoding into files containing Latin-1 or Unicode-encoded charaters.