#27241 OpenAPI: Error although query successful

Enhancement

Critical

#25645

OpenAPI server

#26207

REST calls via TL script to external APIs according to OpenAPI specification

Major

#27196

DeepL: Use glossaries for translations

#27214

TL-Script unversioned object comparison

#27215

Historical to-n references

#27234

Include ChartJS and OpenAPI in BPE Standard Configuration

Detail

#26835

Perform instanceof checks unversioned

#26935

Make Close dialog configurable by Create

#27225

Bulk Dependency Update

#27236

Model definition for revision

#27251

TLModelUtil: Replace declared ConfigurationException with TopLogicException

Bugfix

Critical

#27205

TL-Sync transmitter stops on association update

Major

#27139

Button menu in button bar does not open

#27207

Search suggestions of SelectFields and popups of the breadcrumb are placed incorrectly

#27228

Missing display of Flex data for historical objects

#27241

OpenAPI: Error although query successful

Detail

#26797

Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)

#26921

ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.

#27096

Tree does not scroll the selected node into the viewport on (external) selection

#27167

Normalizing JSPs leads to wrong indentation for if-else blocks

#27203

Application tests with chart.js report on home page fail

#27204

PersistentEnumeration.tValue(...) leads to ClassCastException

#27218

Grid tables: Calculated column: Single-Value SelectField requires list value.

#27227

User time zone and thus SubSession time zone can be zero

#27231

Incremental modification of a set-valued attribute not possible.

#27239

Typo in database configurations at "password template

#27240

OpenAPI: Missing content type for JSON request content

#27249

TLScript suggestions are always displayed in the same language

#27250

Missing Maven profile "ide" in Eclipse

Bugfix

Major

#27241

OpenAPI: Error although query successful

OpenAPI

HTTP status codes 2xx announce "success" in principle. Nevertheless, a query that returns e.g. 204 "No content" crashes.

There is no way to explicitly respond to HTTP status codes. You can only either expect a JSON object, or configure a built-in request check.

Enhancement

It is possible to configure a special post-processing for a set of status codes, or the status code ranges 1XX, 2XX ,3XX ,4XX and 5XX. If the response has none of these status codes, the default handler is used:

Test

Configure an OpenAPI server as a target that returns responses with different status codes.
Configure different handlers for them.
- Expectation: The handler configured for the status code of the response will be executed.