Rafael Winterhalter

There is a good chance for this, I have not looked at the code base for a long time. If you create a PR, I am happy to merge it.

Hi @cowtowncoder, sorry to bother you even more. My current client has a need in this, so I am in the privileged position to put paid time into a PR....

I would certainly keep things backwards compatible but allow for configuration via the module. I will prepare a pull request based on my suggestions, that makes it easier to discuss...

I have an immediate struggle already: How would I handle that I need a dependency on the XML serializer module to support XML serialization. Would introducing such an (optional) dependency...

The problem I am facing is that I can only communicate an additional property by registering an `XmlInfo` object which requires a dependency onto the XML module: https://github.com/raphw/jacksom-xml-see-also/blob/main/src/main/java/org/example/hierarchy/XmlSeeAlsoSerializerWithXmlSupport.java#L68 How would...

If you have an example on how to switch it, any pointer is appreciated! I only found this thread stating that it's not currently possible: https://github.com/FasterXML/jackson-databind/issues/512

This is different to the JAXB case, though. The problem is that the class is represented on the server side as: ```java class Root { @XmlElement(name = "elements") Elements elements;...

Indeed, but the issue is that the two representations in the ticket's description would be both representing the same, valid JAXB structure. I do not think it is currently possible...

I did not manage to make that work as I needed to add XML xsi info. I ended up implementing a custom module, but it feels rather hacky: https://github.com/raphw/jackson-jaxb-extension

Yes, I was just a bit late out. The Maven indices need to sync and I need to update the internal Byte Buddy version which is the last release.