|
I have a deserializer that is used in the binding definition.
<value name="severity" field="severity" deserializer="com.mmm.components.rulechecker.dto.Severity.fromValue" style="attribute" usage="optional"/>
As the attribute is optional, I would expect that Jibx would skip the deserializer and assign “null” to the field directly. It seems that it is calling my deserializer with a parameter or null instead. Is this the intended behavior?
The problem with this is that my deserilializer is a function from an enumeration type (enum pattern in Java) where null is not a valid value…
kind regards
Dr. Hartmut Kocher Cortex Brainware GmbH
|
- [jibx-users] Name not allowed for CDATA (why?) Dr. Hartmut Kocher
- [jibx-users] Name not allowed for CDATA (why?) John Crossman
- Re: [jibx-users] Name not allowed for CDATA (w... Dennis Sosnoski
- Re: [jibx-users] Deserializer called for optional ... Dennis Sosnoski
