PUBLIC MARKS from solrac with tag ejb

This article discusses Crispy, the remote invocation framework. Crispy goal is to provide a single point of entry for remote invocation for a wide number of transports: eg. RMI, EJB, JAX-RPC or XML-RPC. See how it works by using properties to configure a service manager, which is then used to invoke the remote API.

This article covers the API Layer transaction strategy, which is the most robust, simplest, and easiest-to-implement transaction strategy. With that simplicity comes limitations and considerations that this article describes. Learn how to use the EJB 3.0 specification in code examples; the concepts are the same for the Spring Framework and JOTM.

Implementation of successful transaction processing in Java applications is not a trivial exercise. Using examples from the Spring Framework and the Enterprise JavaBeans (EJB) 3.0 specification, this article explains how the transaction models work and how they can form the basis for developing transaction strategies.

Transaction processing should achieve a high degree of data integrity and consistency. This article, the first in a series on developing an effective transaction strategy for the Java platform, introduces common transaction pitfalls that can prevent you from reaching this goal. Using code examples from the Spring Framework and the Enterprise JavaBeans (EJB) 3.0 specification, series author Mark Richards explains these all-too-common mistakes.

The EJB Query Language (EJB QL) allows you to write queries without any knowledge of the relational schema governing the entity beans. This tutorial explains core concepts of the EJB QL with the help of an example Web application using an entity bean that you'll deploy on the Apache Geronimo application server.