Thorsten Hake

I don't think that adding a new response status code is a breaking change according to the spec https://datatracker.ietf.org/doc/html/rfc7231#section-6. Status codes are designed as extensible. Clients need to take this...

According to the "HTTP 1.1 Semantics and Contents" the fallback behavior is a MUST for clients: > HTTP status codes are extensible. HTTP clients are not required to understand the...

@dcustura I would argue that in the case of PUT an optional field is indeed an incompatible change. Omitting an optional field has semantic meaning for PUT. Clients that used...

The error disappears if SkipResolvingEntitiesDocumentBuilderFactory.newDocumentBuilder() no longer returns a cached DocumentBuilder but a fresh one.

It currently does not support JS/native targets. It should be usable on android. I wouldn't know of anything that speaks against using it on android.

Planned to be tackled in version 2.

Closed because of no active discussion

@OneCricketeer thanks for you comment. I'm with you on this. I'll close the issue as not planned.

same here. Seems to me that the soapui maven repo redirects to https://rapi.tools.ops.smartbear.io/nexus/content/groups/public which is down.

Thanks for raising this issue. Unfortunately, Oracle 19c is not supported as of now. But if you can contribute a PR that will make logminer-kafka-connect work for 19c I would...