Versions Compared

Old Version 66

changes.mady.by.user Raúl Kripalani

Saved on

compared with

New Version 67

changes.mady.by.user James Strachan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Refactor the JMS component to remove the dependency on Spring PlatformTransactionManager and replace with JTA TransactionManager.

Default to use Transacted mode by default

One thing I regret about the design of Camel was defaulting to non-transacted mode by default and forcing users to explicitly enable transactional model with a Transaction Manager.

It might be nice in Camel 3 to assume everything is transacted by default; and mimmick a form of transaction manager for non-transactional resource.

e.g. its pretty common to work with messaging like JMS and databases as a common set of endpoints; the easiest thing that could possibly work for end users is for those to just be transacted by default without the user having to grok how to tinker with component configurations & Transaction Manager registration.

Note I'm not advocating XA here; I think the default for camel should be for Idempotent Consumer and simple approach to middleware