MessageRelay | Tox Message Relay | Router library

I don't see @EnableTransactionManagement in account-service, only in message-relay-service.

In any case, your scenario is not currently supported; the transactional binder was designed for processors where the consumer starts the transaction, any records sent on the consumer thread participate in that transaction, the consumer sends the offset to the transaction and then commits the transaction.

It was not designed for producer-only bindings; please open a GitHub issue against the binder because it should be supported.

I am not sure why you are not seeing a transaction starting but, even if it does, the problem is that @Transactional will use Boot's auto-configured KTM (and producer factory) and the binding uses a different producer factory (the one from your configuration).

Even if a transaction is in process, the producer won't participate in it.

You're expecting an object sent to your controller, whether that be Json or XML. But you're encrypting a string in a non-supported format. So when the controller goes to deserialize the message, it can't due to you not using a format.

If you want to use your own specific encryption algorithm you and object format, you will need to take a string into your controller and then deserialize it yourself.

After a lot of search and trying all kinds of things with help of @pringi I returned back to my pom and found out the problem so I thought to write an answer maybe it'll help somebody someday!

The problem was that I had some dependencies in my pom that weren't needed and they could be removed and they conflicted with cxf! So I removed these dependencies and voila!