;
}
});
On Wed, Aug 16, 2023 at 8:19 AM Ken Hancock wrote:
> I think so, but that was my original question -- I couldn't figure out how
> to customize the master to drop that field.
>
> On Tuesday, August 15, 2023 at 9:15:49 PM UTC-4 Joo Hyuk Kim (Vince) wrote:
>
>> Th
erializer from (2) will handle de/serialization for
> specific cases?
>
> ... this, might work?
> On Wednesday, August 16, 2023 at 3:59:26 AM UTC+9 Ken Hancock wrote:
>
>> I can't remove the @JsonAnySetter and @JsonAnyGetter as
>>
>> (1) those are generated a
nce of `SimpleObject` class with
> "onlyField" as its singleField and empty map?
>
> Try simply removing `@JsonAnySetter` and `@JsonAnyGetter`.
>
>
> Hope it helps,
>
> thanks
> On Monday, August 14, 2023 at 11:59:36 PM UTC+9 Ken Hancock wrote:
>
>>
&
ly during
>serialization, but include in deserialization?
>- Is the primary intent to generate a JSON output that does not
>include `additionalProperties`, or is there another objective?
>- Could you also provide a simple, reproducible example using just
>Jackson an
I have a pojo that serializes any additional properties into
@JsonAnyGetter
public Map getAdditionalProperties() {
return this.additionalProperties;
}
@JsonAnySetter
public void setAdditionalProperty(String name, Object value) {
this.additionalProperties.put(name, value);
}
However, I
I have a very large (> JVM memory) payload that requires the extraction of
certain fields for processing. The twist is the fields have escaped json
as the payload. Does Jackson have any capability of parsing this as a
stream?
Example:
{
"field1":"value1",
"field2":"value2",
