Alejandro Revilla

jPOS 2.1.9 was built on Java 11 and targeted Java 8, so it should have worked. This change in ByteBuffer was unexpected. Please check if jPOS 2.1.10-SNAPSHOT solves this issue...

Both vulnerabilities seem to be build time vulnerabilities against Xerces 2.11 not required at runtime. Nothing to worry about IMO, but of course, I can foresee QSAs jumping out of...

I understand your `--ff` option is very similar to what we are suggesting here, and I like it. There's still a difference between failing at startup versus always. I also...

I think what we are addressing here are situations where the TM would drop the QBean descriptor altogether renaming it as `.BAD` or `.DUP` or situations where the QBean raises...

Can you send a PR @barspi ?

@cdanielpy what you report might be related to an issue with your transaction isolation configuration at the JDBC level. Could that be the case?

A change like this deserves the release of `2.2.9` and a move to `2.3.0`. We can do it once you're ready with this PR.

This is not an issue. You're migrating from JDOM 1 series to 2. There's a very good [Migration guide](https://github.com/hunterhacker/jdom/wiki/JDOM2-Migration-Issues).