1.2.2 lambda-java-core release

[andclt]

Description of changes:

August 30, 2022

1.2.2:

• Added new CustomPojoSerializer interface
• Removed unnecessary usage of public on interface methods (removed unnecessary usage of public on interface methods #172)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[msailes]

Why is this moving from the serialization module?

[richarddd]

Wouldn't it also make sense to have a 4th method in the CustomSerializer:
<T> String toJson(T value, Type type);
Then the same serializer instance can be used inside handlers to create event responses requiring json strings

[andclt]

Wouldn't it also make sense to have a 4th method in the CustomSerializer: <T> String toJson(T value, Type type); Then the same serializer instance can be used inside handlers to create event responses requiring json strings

As discussed offline, we do not want to force cx to implement that method when creating a custom serializer. Furthermore, if they want, they can always add it to their custom serializer class.

[pzygielo]

What's T?

[andclt]

It's the type of the deserialized instance

[pzygielo]

I see the intention. But "deserialized plain old java object of type T" uses T which is undefined and unused anywhere else.

Now, in daylight, I see. I was blind.

[msailes]

LGTM