This article discusses an implementation strategy that illustrates how
organizations can use JMS and J2EE Connector technologies to reuse their
infrastructure and lay a foundation that will let them reap the business and
agility benefits of SOA.
For a Service Oriented Architecture (SOA) to be truly resilient, asynchrony
must be built into its fabric. Most large organizations, however, have
already invested in a back-end messaging infrastructure using products such
as MQ Series, Tibco JMS, Oracle Advanced Queuing, Sonic JMS, or SwiftMQ. They
don't want to replace that infrastructure to get to SOA; they want to reuse
it. Enter J2EE 1.4 with two key technologies to enable Web Services and
messaging infrastructure reuse: JAX-RPC, the built-in interoperability-tested
J2EE API for building SOAP-based Web Services; and the J2EE Connector
Architecture, now designed to supp... (more)
The Spring Framework provides a consistent abstraction for transaction
management that delivers the following benefits:
• A consistent programming model across different transaction APIs
such as JTA, JDBC, Toplink, Hibernate, JPA, and JDO
• Declarative transaction management
• A simple API for programmatic transaction management rather than a
number of complex transaction APIs such as JTA
• Integration with Spring's various data access abstractions.
This article discusses Spring's transaction management facilities and the
common use cases in Spring where an ex... (more)