Camel Test with Transactions fails

Solution Unverified - Updated -

Issue

  • We are currently migrating from JBoss Fuse 6.1 to 6.2.1. We are nearly done, but there is one issue which is hindering us to go to production. We cannot get the camel tests running. As soon as there is a transaction definition (e.g. <tx:transaction method=”*” value=”Required” />) in our blueprint files, the camel context in the test cannot be started. There seems to be a problem with resolving the namspace handlers for the transactions.

Environment

  • Red Hat JBoss Fuse.
    • 6.2.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content