1.9. Application servers
Prev | Chapter 1. Kodo JPA/JDO Frequently Asked Questions | Next

## 1.9. Application servers

1.9.1. Can Kodo be run inside an application server?
1.9.2. Which application servers does Kodo support?
1.9.3. Can I integrate Kodo's transactions with the application server's transaction?
1.9.4. Can I use Kodo to implement my bean-managed persistence entity EJBs?

1.9.1. | Can Kodo be run inside an application server?
| Kodo can be used in any J2EE compliant application server. Kodo integrates with managed environments (such as application servers) in a variety of ways, from synchronization with container managed transactions to support for accessing `DataSource`s from JNDI.
1.9.2. | Which application servers does Kodo support?
| Kodo supports any J2EE compliant application server. For ease of configuration and deployment, Kodo recommends (but does not require) using an application server that supports the Java Connector Architecture (JCA). Kodo has been tested with most popular application servers such as JBoss, BEA Weblogic, IBM Websphere, SunONE, Macromedia JRun, and Borland Enterprise Server. See Chapter 8, Deployment.
1.9.3. | Can I integrate Kodo's transactions with the application server's transaction?
| Yes. Kodo can automatically integrate with your application server's managed transactions. See Section 8.2, “Integrating with the Transaction Manager”.
1.9.4. | Can I use Kodo to implement my bean-managed persistence entity EJBs?
| It is possible to use Kodo to implement bean managed persistence (BMP) entity EJBs. However, doing so will introduce the performance penalties incurred by entity beans. The recommended pattern is to use session beans to perform fine-grained persistence operations with Kodo. To get started with using Kodo with EJB 2, see Section 1.3, “J2EE Tutorial”, Section 2.4, “J2EE Tutorial”.

Prev | Up | Next
1.8. Scalability | Home | 1.10. Locking