orderBy
would result in the query to only contain the ordering expression of the last method call. Now, the request will correctly chain the order expressions according to the order in which the method is called.RequestContext
holds central information about the context of the current request, such as the current tenant, destinations, and other information accessed via the SDK's accessor classes. Before introducing the new capability, there could only be one request context (automatically created or manually initiated) and nesting was not possible. Certain scenarios may require initiating a new request context (using a RequestContextExecutor
) in cases where a request context is already present, for example, to switch the tenant context. Now, you can explicitly specify when configuring a RequestContextExecutor
that it is expected that a request context already be present. The executor will execute the wrapped code in the new request context and revert to the parent context afterwards. By default this is disabled and nesting will throw an exception. You must enable this functionality explicitly by using the withParentRequestContext()
method:new RequestContextExecutor()
.withParentRequestContext()
.execute(() -> {
//logic with nested requests
}
sdk-bom
dependency.2.7.0
.<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.sap.cloud.s4hana</groupId>
<artifactId>sdk-bom</artifactId>
<version>2.7.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
<!-- possibly further managed dependencies ... -->
</dependencyManagement>
-DarchetypeVersion=2.7.0
(or RELEASE
).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
4 |