-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird Exception during read with Type info #97
Comments
Interesting... seems odd that ordering of attributes should matter. |
Ok, I've been able to debug the thing, here's what I found: when deserializing with type, when the type property is not the first found, the |
Add missing delegation method. Fix FasterXML/jackson-dataformat-xml#97.
Very good detective work... |
Looks like 'bad' test still fails tho? |
I've hit a rather nasty problem when deserializing some XML, which seems to be caused by the order the attributes appear on an xml element. For exemple
<Foo type=\"bad\" data=\"dummy\"><bar><bar>FOOBAR</bar></bar></Foo>
parses fine, but invertingtype
anddata
attributes' order result in this weird exception:I've also noted that this doesn't cause problem when the property is not a List. I'll attach a unit test shortly.
I've debugged a little bit and it seems that because the
type
property is not the first encountered during parsing there's some buffering (withTokenBuffer
) involved, which doesn't seem to play well with the Collection deserializer. This might also be related to the virtual wrapping necessary for collections?The text was updated successfully, but these errors were encountered: