Fixed #39 #36

[SravanThotakura05]

No description provided.

[ozangunalp]

👍 I forgot about the missing-resource-creation-strategy=create-on-start

I noted a couple of changes that'll make the example a bit more coherent.

Also, I've noted that in dev mode the queue.dynamic.topic incoming channels consume messages from the beginning of the queue, and I see in the Solace UI that "messages queued" get stacked up. Does that mean we have problem with sending acknowledgements to the broker?

[SravanThotakura05]

👍 I forgot about the missing-resource-creation-strategy=create-on-start

I noted a couple of changes that'll make the example a bit more coherent.

Also, I've noted that in dev mode the queue.dynamic.topic incoming channels consume messages from the beginning of the queue, and I see in the Solace UI that "messages queued" get stacked up. Does that mean we have problem with sending acknowledgements to the broker?

Earlier we are creating a outbound message with ack and nack callbacks which used to trigger acks to broker. Since we removed it i believe it is not calling the ack method which sends ack to broker

[ozangunalp]

Ok actually this exposes something missing from the SolaceInboundMessage. For the message ack composition to work we need to override getAck / getNack methods in the message implementation.
Like this:

    @Override
    public Supplier<CompletionStage<Void>> getAck() {
        return this::ack;
    }

[SravanThotakura05]

@ozangunalp all comments are addressed