Releases: palantir/conjure-java-runtime-api
Releases · palantir/conjure-java-runtime-api
2.5.0
| Type | Description | Link |
|---|---|---|
| Improvement | ServiceException retains the errorInstanceId from its cause, allowing RemoteExceptions to be caught and used as the cause for as more specific ServiceException without sacrificing observability. In most cases a single error identifier query is sufficient to discover the root cause of a failure instead of individually requesting each segment back to the root. |
#348 |
2.4.0
2.3.0
-
[fix][break] fix #148: ServiceException.getMessage includes unsafe args (#158)
This change provides parity with safe-logging Safe*Exception types, see palantir/safe-logging#76
By providing all argument data in the exception message we provide full context to logging systems which do not understand safe-logging types.
2.2.0
2.1.0
1.11.0
2.0.0
We're rebranding http-remoting-api to be a part of the 'Conjure' ecosystem.
- maven group changed:
com.palantir.remoting-api->com.palantir.conjure.java.api - packages changed:
+com.palantir.conjure.java.api.errors
-com.palantir.remoting.api.errors- deleted deprecated code
- moved tracing classes to https://github.com/palantir/tracing-java
- new
com.palantir.conjure.java.api.config.service.UserAgentclass from http-remoting
1.11.0-rc2
- More asConjure methods (#118)
// tagged on develop