Ayesh Almeida

@warunalakshitha / @HindujaB any idea on how to fix this ?

Proposal has been added here [1] [1] - https://github.com/ballerina-platform/ballerina-library/issues/6517

Proposal has been added here [1] [1] - https://github.com/ballerina-platform/ballerina-library/issues/6515

Reopening this issue as we have reverted the change with this [1] [1] - https://github.com/ballerina-platform/ballerina-library/issues/6628

The proposal for the implementation can be found here [1] [1] - https://github.com/ballerina-platform/ballerina-library/issues/6508

> * Do we need to pass `asb:Message` for the caller functions? Can't we omit it and retrieve the context from the caller? So user can just call complete once...

In the proposed `asb:Caller` API the `defer` method has the following signature, ```ballerina public type Caller distinct client object { // other methods isolated remote function defer(*record {|anydata...;|} propertiesToModify) returns...

> Using `autoComplete` mode > When `autoComplete` mode is enabled, explicit acknowledgment or rejection of messages (ack/nack) by the caller is unnecessary. Therefore, if `autoComplete` is active and the developer...

> `asb:Caller` is used not just for ack/nack functionality. it also enables users to mark messages as `defer` and move them to the dead letter queue. Therefore, if we restrict...

This has been implemented with this PR [1] and the proposal-doc was added to the repository with this PR [2] [1] - https://github.com/ballerina-platform/module-ballerinax-azure-service-bus/pull/220 [2] - https://github.com/ballerina-platform/module-ballerinax-azure-service-bus/pull/222