## +21 ## Custom Views for the Rest of Us ## JACOB RICE 20 21 October 24-29 ## Custom Views for the Rest of Us Jacob Rice jacob.rice.cpp@gmail.com KEYSIGHT TECHNOLOGIES 1 using namespace std::views;

Integration Version 5.3.36-SNAPSHOT ## Table of Contents 1. REST Endpoints ..... 2 1.1. RestTemplate ..... 2 1.1.1. Initialization ..... 3 URIs ..... 3 Headers ..... 4 1.1.2. Body ..... 4 Messages Within Transactions ..... 43 4.4. Support for JCA Message Endpoints ..... 44 4.5. Annotation-driven Listener Endpoints ..... 46 4.5.1. Enable Listener Endpoint Annotations ..... 47 4.5 of technologies. ### Chapter 1. REST Endpoints The Spring Framework provides two choices for making calls to REST endpoints: • RestTemplate: The original Spring REST client with a synchronous, template

Tests ..... 134 Auto-configured Data LDAP Tests ..... 135 Auto-configured REST Clients ..... 136 Auto-configured Spring REST Docs Tests ..... 137 Auto-configured Spring Web Services Tests ..... 143 2.5. Elasticsearch ..... 240 Connecting to ElasticSearch using REST clients ..... 240 Connecting to ElasticSearch using Reactive REST clients ..... 241 Connecting to ElasticSearch by Using Spring 11.2. Quartz Scheduler 283 11.3. Sending Email 285 11.4. Validation ..... 286 11.5. Calling REST Services ..... 287 11.5.1. RestTemplate ..... 287 RestTemplate Customization ..... 288 11

12.5. Elasticsearch ..... 181 Connecting to Elasticsearch using REST clients ..... 181 Connecting to Elasticsearch using Reactive REST clients ..... 182 Connecting to Elasticsearch by Using Spring with Embedded Kafka ..... 218 7.15. Calling REST Services with RestTemplate ..... 219 7.15.1. RestTemplate Customization ..... 220 7.16. Calling REST Services with WebClient ..... 222 7.16.1. WebClient Tests ..... 259 Auto-configured Data LDAP Tests ..... 260 Auto-configured REST Clients ..... 261 Auto-configured Spring REST Docs Tests ..... 262 Auto-configured Spring Web Services Tests ..... 268

DataBinder 61 Model Design 63 1.4.6. Managing Exceptions 64 REST API exceptions 65 1.4.7. Controller Advice 66 1.5. Functional Endpoints 67 1.5.1. Overview 67 1.5.2. HandlerFunction 69 ServerRequest resources. Servlet 3.1 did provide an API for non-blocking I/O. However, using it leads away from the rest of the Servlet API, where contracts are synchronous (Filter, Servlet) or blocking (getParameter, getPart) programming. Much as the addition of annotations in Java 5 created opportunities (such as annotated REST controllers or unit tests), the addition of lambda expressions in Java 8 created opportunities for

Additional Kafka Properties ..... 131 33. Calling REST services with 'RestTemplate' ..... 133 33.1. RestTemplate customization ..... 133 34. Calling REST services with 'WebClient' ..... 135 tests ..... 157 Auto-configured Data LDAP tests ..... 157 Auto-configured REST clients ..... 158 Auto-configured Spring REST Docs tests ..... 158 Using Spock to test Spring Boot applications ..... 170 49. Endpoints ..... 171 49.1. Customizing endpoints ..... 172 49.2. Hypermedia for actuator MVC endpoints ..... 173 49.3. CORS support ..... 173 49.4. Adding custom endpoints ..... 173

Frequently Asked Questions • Supported file formats • Version control integration • Weblate's REST API • Weblate Client • Weblate's Python API ## Administrator docs • Configuration instructions in version 2.3. This adds a thin layer atop Git using the Github API [https://docs.github.com/en/rest] to allow pushing translation changes as pull requests, instead of pushing directly to the repository Weblate's REST API New in version 2.6: The REST API is available since Weblate 2.6. The API is accessible on the /api/ URL and it is based on Django REST framework [https://www.django-rest-framework

Questions 69 1.10 Supported file formats 77 1.11 Version control integration 98 1.12 Weblate's REST API 105 1.13 Weblate Client 153 1.14 Weblate's Python API 158 2 Administrator docs 161 on. ### 1.12 Weblate's REST API New in version 2.6: The REST API is available since Weblate 2.6. The API is accessible on the /api/ URL and it is based on Django REST framework. You can use it directly status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (override Accept). Possible values depend on REST framework setup, by default json and api are

importance de l'architecture : – orientée ressource $ ^{1} $ : atome : ressource (donnée) : REST – orientée service $ ^{2} $ : atome : service (traitement) : RPC (SOAP) ## Service web ## • 2 visions annuaire d'interfaces de services web décrites en WSDL • Tutorial WSDL/UDDI w3schools $ ^{11} $ ## REST : REpresentational State Transfer • Style d'architecture sur lequel a été bâti le web • Architecture forme donnée à la ressource - ex. : page html, fichier PDF, image, flux RSS, fichier sonore, ... ## REST ## • Principes – Identifier les ressources avec des URI (noms) – Actions déterminées par des méthodes

8 翻译工作流 60 1.9 Frequently Asked Questions 63 1.10 支持的文件格式 70 1.11 版本控制集成 88 1.12 Weblate 的 REST API 95 1.13 Weblate 客户端 134 1.14 Weblate's Python API 138 2 Administrator docs 140 2.1 integration on. ### 1.12 Weblate 的 REST API 2.6 新版功能: The REST API is available since Weblate 2.6. The API is accessible on the /api/URL and it is based on Django REST framework. You can use it directly status codes and parameters here apply to all endpoints as well. ## Query Parameters • format –Response format (override Accept). Possible values depend on REST framework setup, by default json and api are