ROME | Aqueduct - "Piping Feeds for Rome"

The ROME | Aqueduct project will allow the persistence of SyndFeed and its composition objects (SyndImage, SyndEntry, etc.) in various persistence mechanisms. (Not just databases!).

Now that we have a DAO layer of interfaces, we plan to provide implementations which use Hibernate and other ORM technologies to save SyndFeeds into various persistence mechanisms.

Aqueduct Data Access Object (DAO) API

Our RFC (Request For Comments) for the DAO API is complete. We have developed a backend-agnostic DAO interface layer that all Aqueduct implementations will use to persist/retrieve feeds. Taking Hibernate, Castor and other potential persistence mechanisms into account, we have provided these DAO interface definitions:

• Aqueduct DAO Javadoc
• Aqueduct DAO Class Diagram

We invite your feedback! If you are interested in implementing the ROME Aqueduct DAO layer, please discuss on the rome-dev or rome-user mailing lists.

Aqueduct Implementations

We have plans to provide several implementations of the Aqueduct DAO API to meet a variety of persistence needs. Keep checking this list, as it will grow over time.

• Prevayler: Mark implemented persistence for SyndFeeds using Prevayler. The Aqueduct-Prevayler Distribution is in its very early stages, but could still be useful. See the ROME Aqueduct - Prevayler Implementation page for more information.

• Hibernate: Amin implemented persistence for SyndFeeds using Hibernate prior to the creation of the Aquduct subproject. We hope to have his implementation updated to implement the Aqueduct DAO in the near future.