XML attributes are not correctly populated when converting from XML (ObjectNode) to String using writeValueAsString (XML structure)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Comienza con el driver de ejemplo que utiliza XmlMapper.readTree y writeValueAsString; después, inspecciona el AnimalDeserializer.java personalizado y su método readObjectNodeAsString. Compara el ObjectNode analizado con el XML esperado, incluidos los atributos y las declaraciones de espacio de nombres; se considera terminado cuando la conversión conserva esos atributos y espacios de nombres en lugar de emitir elementos secundarios.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi @cowtowncoder,
We are planning to migrate our old deserialization logic from using fragmented substrings between <open> and </closing> tags when deserializing an XML String to POJOs into Jackson’s sophisticated custom StdDeserializers/JsonDeserializers directly starting from version 2.15.2.
I have a few questions about whether this feature of mine already exists or not.
My team and I are trying to deserialize a very complex XML structure, to the point that we do not have to create multiple beans because some of the content of our XML subtree often changes dynamically with minimal format structure (we have ~10 XML formats to support with or without attributes and namespaces) and is also a valid XML structure. WE mostly used custom deserializers like StdDeserializer and JsonDeserializer to map ObjectNode into plain Map (well internally, this is already a Map) (thanks for your suggestion in #574) and then later converted it back to String.
While I still stumbled across our implementation to keep our XML subtree to be deserialized via substring. But then later we planned to stick to using JsonNode to retrieve segments of XML and convert it back to the original XML as String using SegmentedStringWriter#writeValueAsString, for a reason that we wanted to leverage the java.xml.stream.* without the need to retrieve full string token and to fully adapt Jackson's Streaming API interoperability. We do not want to convert it into a plain POJO, but instead, would rather use the java.util.Map class to keep it generic and to store every JsonNode token retrieved from ObjectNode#getValue().
Sample Scenario
Supposedly, I have an XML element that contains an attribute name and age.
<animal>
<dog name="tucker" age="2">woof woof!</dog>
<cat name="cody" age="2">meowwwwwww!</cat>
<chicken name="browny" age="3">cluck cluck!</chicken>
<pig name="porky" age="4">oink oink!</pig>
</animal>
XML Attribute
The output I would expect should be the same as the original XML, but in my case, it's not:
<animal>
<dog>
<name>tucker</name>
<age>2</age>
<>woof woof!</>
</dog>
<cat>
<name>cody</name>
<age>2</age>
<>meowwwwwww!</>
</cat>
<chicken>
<name>browny</name>
<age>3</age>
<>cluck cluck cluck cluck!</>
</chicken>
<pig>
<name>porky</name>
<age>4</age>
<>oink oink!</>
</pig>
</animal>
The attributes became sub-elements of the original element, while the element tag of the original element value becomes empty: <>...</>
XML Namespace
The same happens with namespaces:
suppose Animal namespace declaration: <ns1:animal xmlns:ns1="urn:this:is:namespace:for:animal">
Output:
<animal>
<xmlns:ns1>urn:this:is:namespace:for:animal</xmlns:ns1>
<ns1:dog>
<name>tucker</name>
<age>2</age>
<>woof woof!</>
</ns1:dog>
<!-- ... -->
</animal>
The namespace becomes a new element.
My assumption is that it will only work with a plain XML structure (excluding the attributes itself) or with bean-defined POJOs annotated XML attr properties.
Sampe Driver Code
Tried using custom XmlMapper config:
private static XMLInputFactory xmlInputFactory() {
final XMLInputFactory factory = XMLInputFactory.newInstance();
factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE, false);
return factory;
}
OBJECT_WRITER = new XmlMapper(xmlInputFactory(), customJacksonXmlModule())
.configure(ToXmlGenerator.Feature.WRITE_XML_DECLARATION, true)
.enable(SerializationFeature.INDENT_OUTPUT)
.writer();
JsonNode node = mapper.readTree(
"<animal>\n"
+ " <dog name=\"tucker\" age=\"2\">woof woof!</dog>\n"
+ " <cat name=\"cody\" age=\"2\">meowwwwwww!</cat>\n"
+ " <chicken name=\"browny\" age=\"3\">cluck cluck!</chicken>\n"
+ " <pig name=\"porky\" age=\"4\">oink oink!</pig>\n"
+ " </animal>");
System.out.println(mapper.writer().withDefaultPrettyPrinter().withRootName("animal").writeValueAsString(node));
and with a custom deserializer for the Animal bean.
@JsonDeserialize(using = AnimalDeserializer.class)
class Animal {
String xmlContent; // <-- JsonNode to String: <dog name="tucker" age="2">woof woof!</dog>...
}
AnimalDeserializer.java
@Override
public T deserialize(JsonParser parser, DeserializationContext context) throws IOException {
final ObjectCodec codec = parser.getCodec();
final ObjectNode objectNode = codec.readTree(parser);
final T object = codec.readValue(objectNode.traverse(), getValueType(context));
final Iterator<Entry<String, JsonNode>> nodeIterator = objectNode.fields();
while (nodeIterator.hasNext()) {
Entry<String, JsonNode> nodeEntry = nodeIterator.next();
// we manually set the value for non-annotated @JsonProperty() fields, let Jackson take care for us!!
if (!attributes().contains(nodeEntry.getKey())) {
if (nodeEntry.getValue() instanceof ObjectNode) {
object.setContent(readObjectNodeAsString(nodeEntry));
}
...
}
}
return object;
}
private String readObjectNodeAsString(Entry<String, JsonNode> nodeEntry) {
try {
return OBJECT_WRITER
.withRootName(nodeEntry.getKey())
.writeValueAsString(nodeEntry.getValue());
}
...
}
Update:
When using TypeReference<Map<String, String>(){}, it prints the expected XML output. However, the attribute is still missing.
Map<String, String> node = XML_MAPPER.readValue("...", new TypeReference<Map<String, String>>() {});
Output:
<?xml version='1.0' encoding='UTF-8'?>
<animal>
<dog>woof woof!</dog>
<cat>meowwwwwww!</cat>
...
We really appreciate your feedback and suggestions for this @cowtowncoder
- Lenguaje dominante
- Java
- Estrellas
- 636
- Forks
- 250
- Merge medio
- 7 h 10 min
- PR fusionados (30 d)
- 8
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FasterXML/jackson-dataformat-xml
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
FasterXML/jackson-dataformat-xml#931 · 3 comentarios ·
-
XmlMapper with `FAIL_ON_UNKNOWN_PROPERTIES` fails on whitespace-only elementPosiblemente ocupada @arimu1 la tomó hace 89 días. Abiertoto-evaluate
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
-
3.x
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
FasterXML/jackson-dataformat-xml#787 · 1 comentario ·
Todos los issues de FasterXML/jackson-dataformat-xml
Issues similares
-
Cleanup: restore the interrupt flag in AiFailureAnalyzerPosiblemente ocupada @Rishankgupta08 la tomó hoy. Abiertogood first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
seleniumboot/selenium-boot#258 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
dense-analysis/ale#5181 ·
-
bug subsystem:agent-harness triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ShaftHQ/SHAFT_ENGINE#8043 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
johanhaleby/occurrent#1505 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día