Figure 3.4 The datasource bundle provides three datasource services. The first and third were explicitly
configured in the blueprint.xml, but the second was automatically created by the container to provide
support for implicit transactions.
interface, as expected by JPA , but it provides an extra function built around the
XADataSource you registered, to provide full container-managed transaction support
This has perhaps been more work than you expected to have to do to set up a data-
source. It's important to remember that the assembly shipped with the Apache Aries
samples isn't a proper application server, or even half an application server. If you opt
Figure 3.5 The fancyfoods
.datasource bundle explicitly de-
clares two datasource services. A
third service that consumes the
XADataSource is automatically
registered by the container.