Java Record with @JacksonXmlText stop working with 2.18

[akastyka]

Search before asking

• I searched in the issues and found nothing similar.

Describe the bug

Following class can't be deserialized with Jackson 2.18.2:
public record Variable( @JacksonXmlProperty(isAttribute = true, localName = "name") String name, @JacksonXmlText String value) {}

deserialization fails with:
Invalid definition for property '' (of type com.Variable): Could not find creator property with name '' (known Creator properties: [name, value]) at [Source: (StringReader); line: 1, column: 1]

it works with Jackson 2.17.2. Also it works with 2.18.2 but with POJO only

Version Information

2.18.2

Reproduction

-->

public record Variable(
        @JacksonXmlProperty(isAttribute = true, localName = "name") String name,
        @JacksonXmlText String value) {
    public static void deserialize() throws JsonProcessingException {
        XmlMapper xmlMapper = new XmlMapper();

        Variable deserialized = xmlMapper.readValue(
                "<jackson name=\"value\">test</jackson>", Variable.class);
        System.out.println(deserialized);
    }
}

Expected behavior

Java record is deserialized

Additional context

No response

[pjfanning]

just in case, could you try 2.18.3?

[akastyka]

Same issue with 2.18.3

[cowtowncoder]

XML-specific, will move to proper repo.

[pjfanning]

this looks a bit like #739 which was written for #734

[cowtowncoder]

Closed #734 in favor of this one.

Suspecting that marker "" for @JacksonXmlText getting wrongly associated might be causing/related to the issue here.
Although Property introspection changes in 2.18 also likely related. But quite odd things work with POJOs with same annotations... handling differs, but 2.18 handles Records more similarly to POJOs that 2.17.

[pjfanning]

Closed #734 in favor of this one.

Suspecting that marker "" for @JacksonXmlText getting wrongly associated might be causing/related to the issue here. Although Property introspection changes in 2.18 also likely related. But quite odd things work with POJOs with same annotations... handling differs, but 2.18 handles Records more similarly to POJOs that 2.17.

#734 (comment) seems to suggest that creating a class with the equivalent definition to a record works better in 2.18 than the record.