Skip to content

WebFluxOutboundChannelAdapterParser silently ignores encoding-mode attribute if web-client attribute is present #3954

@aljopainter

Description

@aljopainter

In what version(s) of Spring Integration are you seeing this issue?

2.7.1 but I believe that 6.0.0 also has this problem

Describe the bug

When the web-client attribute is included in the declararation of a webflux:outbound-gateway using XML namespace support, the encoding-mode attribute will be ignored silently because the encoding mode from the UriBuilderFactory of the web-client will be used instead.

To Reproduce

Include an encoding-mode attribute and a web-client with a different encoding-mode within the UriBuilderFactory.

Expected behavior

An error or warning to signal that encoding-mode is ignored.

Sample

Similar to #3939

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions