WP-API | WP REST API has been merged into WordPress core | REST library

Since I didn't find any solution for that, I've implemented method for GET-requests: https://gist.github.com/Blackmorse/cdb5e13d749e7902ad47d5a168dd23ca

Usage: E.g. you want request data from s"$URL/$API_ENDPOINT?param1=value1&param2=value2".

To construct the Akks's akka.http.scaladsl.model.HttpRequest object:

Try this, this should do what you are asking.

In my case it was an additional plugin called "Password Protected". This one forced a cookie authentication for every call to the wordpress instance. Even for calls to wp-json. After deactivating the plugin, the problem had disappeared.

I finally got the answer after 2 days

The best solution is to remove all the above and just add

You may can use wp_remote_retrieve_body($url) OR wp_remote_post($url) to grab post data instead of rest API usage. wp_remote functions are independent of default pagination.

This happens often when you're trying to place Scrollable widget into an infinite heigth widget or infinite heigth (Column) widget into scrollable (SingleChildScrollView,ListView) .

This means you're trying to use SingleChildScrollView> Column> ListView> Column

You should add following property to Column an ListView

Looking at the dependency tree, I can see that there is a mix-up of SDK dependencies of version 2 and 3 in your project which is causing the issue.

The dependency entries with groupId starting with com.sap.cloud.s4hana are mostly v2 dependencies and the ones with groupId starting with com.sap.cloud.sdk are v3 dependencies.So, please use this as a reference to convert all v2 dependencies to the corresponding v3 dependencies.

Alternatively, you can also include the sdk-bom dependency (groupId: com.sap.cloud.sdk, artifactId: sdk-bom ) in your pom with a version, so that you can start including other sdk dependencies without explicitly including the version information. This would also ensure that all the sdk dependencies you include would always fall into the a particular version:

Thanks for the good question. The first thing I've noticed you're using an already quite outdated version of the SDK, the current one is 3.14.0, you're on the 3.2.0 at the moment. We do a lot of fixes with every release and I would recommend switching to the latest one in your dependencies. Take a look in our release notes

In regards to Resilience, it's hard to tell exactly why the load test might fail because you use SDK on quite a low level by invoking an un-typed request builder that is not maintained by the SDK team. For Odata V2 ODataCreateRequestImpl is a dependency and not meant for direct consumption. We expose it only for edge cases and convenience.

A more reliable way to use SDK would be to generate a Virtual Data Model from your service definition first and then build typed requests. Those should be more reliably implemented and easier to debug.

• Is it an option for you to generate the Virtual Data Model first and use the preferable way of building requests? This tutorial covers the topic of the way SDK is intended to be used for the most use cases
• Here is the tutorial covering basic Resilience setup

I'll see if I can find more ideas about this case, in the meanwhile updating the SDK version and checking if you can use typed request builders mentioned in the tutorials above for CRUD would be a good idea.

If you have any additional details that might shed more light on this case, feel free to share them.

I assume you used the generator to generate the VDM based on the metadata. If so and if possible, please share the metadata.

Assuming the above, the field that you are trying to use does not and is not meant to hold any data. It is to be used when building OData requests, so in select and filter operations.

In order to access the data you would indeed need getters on the entity type. Be sure to include lombok as dependency in your project as we use the @Data annotation in the generated code: