Tristan Tarrant
Tristan Tarrant
Infinispan 14.0.0.CR2 has removed the `jakarta` classifier and now ships artifacts such as `infinispan-client-hotrod-jakarta`
There is a conflict
I'm wondering if a catch-all generic "binary" 1:1 transcoder wouldn't be a better idea. From the REST point-of-view it could also add a `Content-Disposition: attachment; filename="key"` header
The query endpoint returns errors differently from every other endpoint, by returning a JSON in the HTTP content. While it does provide a bit more structure, I feel it should...
Merged, thanks
I doubt the spring boot version matters much here, since it is the hot rod client which is performing the connection. Can you share the client configuration properties?
Can you provide the dependency tree which starts from the Infinispan components? mvn dependency:tree On Sat, 20 Mar 2021, 18:24 giosefer, ***@***.***> wrote: > thanks for you information. > This...
The best thing to do is to get TRACE logs for `org.infinispan` in your client, so we can see what happens.