Disable PojoResourceTest due to issue on Yasson 3.0.1

[loicmathieu]

Fixes #27506

Disable test that fails in Jakarata EE migration due to Yasson 3.0.1 bug eclipse-ee4j/yasson#575
An issue has been openned to remember to re-enable it in the future see #27619

[gsmet]

@loicmathieu I'm not sure I understand the issue you created. You created an issue for serialization of null Optionals but I see you're defining a value here?
And... if it's just an issue with null optionals, maybe we can simply define a value where it's missing?

[loicmathieu]

I'll check what's going on, I think the same issue occurs when deserializing and that causes some issue somewhere. I'll switch to the jakarta rewrite branch and test again to have the exact exception.

[loicmathieu]

@gsmet maybe there is also an issue with Optional serialization but when I test manually the endpoint what fails is serialization not deserialization. Let's disable the test and see what they have to say at Yasson side, when/if they provide a fix I'll re-enable the test and see if more issue exist.

[gsmet]

Well my problem is that you opened an issue about null optionals and in the test you are pushing a value. That's what I don't understand.

[gsmet]

To clarify: I want to make sure we reported the issue properly.

[loicmathieu]

In fact, deserialization of Optional didn't seems to work either, it leads to a null value in database that why the serialization throws a NPE.

As the provided test have both serialization and deserialization, they may fix both (or as I said, I'll work with them to fix that).

[gsmet]

OK, thanks!