An important new feature in this release is the support for transactional JMS message listeners, meaning that message-driven applications can be developed and run without the need for EJB or an application server. The transaction support avoids message loss and/or duplicate messages. Queue bridging (across JMS domains) is also provided.
When combined with IoC/AOP frameworks like Spring, POJO applications obtain message-driven and transactional services comparable to EJB, but without the requirement for an application server.
Main new features of Transactions 2.10:
- Transactional message listener support
- Queue bridging: bridge messages across queue domains, without message loss or duplicates
- JBoss 4 support
- Console file rotation
- JCA 1.5 inbound transaction support
- Spring support
- A transactioning micro-kernel: very compact yet very powerful
- Distributed transactions across almost any type of resource
- Extremely fast JTA: XA transactions at local transaction performance
- Nested transactions for increased fault-tolerance
- Two-phase commit with extensive heuristic support for increased autonomy
- Read-only optimization for increased performance
- Decentralized design, for perfect scalability and peer-to-peer transactioning
- JTA compatibility
- JDBC support
- JMS support, including transactional message listeners and queue bridging
- Synchronization callback support
- RMI (JRMP and IIOP) support
- Distributed recovery included
- J2SE support included
- J2EE support included: integrates with most J2EE platforms