Split JPA Outbound Gateway into "updating-outbound-gateway" and "retrieving-outbound-gateway" [INT-2582]

[spring-operator]

Gunnar Hillert opened INT-2582 and commented

The JPA Outbound Gateway currently has an attribute gateway-type. The type value will trigger different methods being called in the underlying JpaExecutor class. Each of those 2 method calls has (with overlap) a different set of attributes.

Therefore, in order to make the configuration much clearer, split the namespace definition into 2 components:

<int-jpa:updating-outbound-gateway />

Unique properties:

• persistMode

<int-jpa:retrieving-outbound-gateway />

Unique properties:

• deleteAfterPoll
• expectSingleResult
• deletePerRow

---

Affects: 2.2 M1

Sub-tasks:

• Need a mechanism to have the max-number-of-results attribute for JPA outbound gateway and inbound adapters [INT-2573] #6557 Need a mechanism to have the max-number-of-results attribute for JPA outbound gateway and inbound adapters

Issue Links:

• Update the JPA Adapter Documentation reflecting the Outbound Gateway Changes [INT-2601] #6581 Update the JPA Adapter Documentation reflecting the Outbound Gateway Changes
  ("is depended on by")

[spring-operator]

Gunnar Hillert commented

The original title was "For JPA Outbound Gateway - change gateway-type to type". But after some consideration it will be better to separate the namespace definition for the Outbound Gateway into 2 separate Outbound Gateway components.

[spring-operator]

Gunnar Hillert commented

Issued PR: #465

Fixed:

• Split JPA Outbound Gateway into "updating-outbound-gateway" and "retrieving-outbound-gateway"
• Need a mechanism to have the max-number-of-results attribute for JPA outbound gateway and inbound adapters [INT-2573] #6557 Need a mechanism to have the max-number-of-results attribute for JPA outbound gateway and inbound adapters
• Cleanup
• Add more comments
• Add unit tests