Use configured encoding during JiBX unmarshalling
Before this change JibxMarshaller did not use the configured encoding when unmarshalling XML. This caused issues when content being unmarshalled was not encoded using the default encoding. This commit fixes the issue by passing configured encoding to JiBX so it gets used when unmarshalling instead of the default encoding. Issue: SPR-7865
This commit is contained in:
committed by
Chris Beams
parent
e3f544904c
commit
e25183eab1
@@ -8,6 +8,7 @@
|
||||
</mapping>
|
||||
<mapping name="flight" class="org.springframework.oxm.jibx.FlightType">
|
||||
<namespace uri="http://samples.springframework.org/flight" default="elements"/>
|
||||
<value name="airline" field="airline" usage="optional"/>
|
||||
<value name="number" field="number" usage="required"/>
|
||||
</mapping>
|
||||
</binding>
|
||||
|
||||
Reference in New Issue
Block a user