This seems unfortunate, and I think is just a kink of the way structural impedance between XML and JSON is resolved (JSON does not have names for Object, only for properties; XML elements/attributes always have names).
Could you file in issue against `jackson-dataformat-xml` for this please? (unless there is one filed, which is possible). Ideally it would be verified, along with namespace. -+ Tatu +- On Wed, Jun 21, 2017 at 7:25 AM, Leonard Meyer <[email protected]> wrote: > Hi, > > So I don't know if this is expected behavior, but the localName attribute of > @JacksonXmlRootElement is not enforced during deserialization. In other > words, if I want the input to be > > <test> > <inner>1</inner> > </test> > > And I get > > <ohnoes> > <inner>1</inner> > </ohnoes> > > > inner will still be deserialzed properly. This seems weird to me. Here is a > fully reproductible test > > > > > -- > You received this message because you are subscribed to the Google Groups > "jackson-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
