    META TOPICPARENT    name="Rome"
-   META TOPICPARENT
+ name="Rome"
-<
<
+ Rome | Aqueduct - "Piping Feeds for Rome"
->
>
+ 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!).
->
>
+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 DAO Javadoc
  Aqueduct DAO Class Diagram
-<
<
+We invite your feedback!  If you are interested in implementing the Aqueduct DAO layer, please do so on the rome-dev or rome-user mailing lists.
->
>
+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 Aqueduct - Prevayler Implementation page for more information.
->
>
+ 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.

<<O>> Difference Topic RomeAqueduct (6 - 24 Mar 2005 - Main.markwoodman)

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="Rome"

Rome | Aqueduct - "Piping Feeds for Rome"

<<O>> Difference Topic RomeAqueduct (5 - 17 Mar 2005 - Main.markwoodman)

Line: 1 to 1
	Rome \| Aqueduct - "Piping Feeds for Rome"
Line: 19 to 19
	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.
Changed:
< <	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. In the mean time, if you need to persist SyndFeeds^? right now you can check out the Hibernate subproject in CVS.
> >	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 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.

<<O>> Difference Topic RomeAqueduct (4 - 12 Mar 2005 - Main.markwoodman)

-<
<
+ Rome Aqueduct - "Piping Feeds for Rome"
->
>
+ 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 databases.
->
>
+The Rome | Aqueduct project will allow the persistence of SyndFeed^? and its composition objects (SyndImage^?, SyndEntry^?, etc.) in various persistence mechanisms. (Not just databases!).
-<
<
+Our current plans are to determine a DAO layer of interfaces, then provide implementations which use Hibernate or Castor to save feeds to MySQL^?, HSQLDB, and other 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.
-<
<
+ RFC : DAO Layer
->
>
+ Aqueduct Data Access Object (DAO) API
-<
<
+We are developing a backend-agnostic DAO interface layer that all Aqueduct implementations will use to persist/retrieve feeds.	Taking Hibernate and Castor into account as potential persistence mechanisms, we propose this initial set of DAO interface definitions:
->
>
+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
->
>
+ Aqueduct DAO Class Diagram
-<
<
+We invite your feedback!  If you are interested in commenting on the proposed DAO layer, please do so on the rome-dev or rome-user mailing lists.
->
>
+We invite your feedback!  If you are interested in implementing the Aqueduct DAO layer, please do so 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.
 

 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.	In the mean time, if you need to persist SyndFeeds^? right now you can check out the Hibernate subproject in CVS.

<<O>> Difference Topic RomeAqueduct (3 - 17 Feb 2005 - Main.markwoodman)

Line: 1 to 1
	Rome Aqueduct - "Piping Feeds for Rome"
Line: 13 to 13
	Aqueduct DAO Javadoc Aqueduct DAO Class Diagram
Changed:
< <	We invite your feedback! If you are interested in commenting on the proposed DAO layer, please do so on the rome-dev mailing list.
> >	We invite your feedback! If you are interested in commenting on the proposed DAO layer, please do so on the rome-dev or rome-user mailing lists.

<<O>> Difference Topic RomeAqueduct (2 - 12 Feb 2005 - Main.markwoodman)

-<
<
+ Rome Aqueduct
->
>
+ 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 databases.
-<
<
+Coming Soon!
->
>
+Our current plans are to determine a DAO layer of interfaces, then provide implementations which use Hibernate or Castor to save feeds to MySQL^?, HSQLDB, and other databases.

 RFC : DAO Layer 

We are developing a backend-agnostic DAO interface layer that all Aqueduct implementations will use to persist/retrieve feeds.	Taking Hibernate and Castor into account as potential persistence mechanisms, we propose this initial set of DAO interface definitions:
 

 Aqueduct DAO Javadoc
  Aqueduct DAO Class Diagram
 

We invite your feedback!  If you are interested in commenting on the proposed DAO layer, please do so on the rome-dev mailing list.

<<O>> Difference Topic RomeAqueduct (1 - 10 Feb 2005 - Main.markwoodman)

Line: 1 to 1

Added:

>
>

Rome Aqueduct

The Rome Aqueduct project will allow the persistence of SyndFeed and its composition objects (SyndImage, SyndEntry, etc.) in various databases.

Coming Soon!

Topic RomeAqueduct . { View | Diffs r7 < r6 < r5 < r4 | More }

java.net RSS