I've written a simple example application that shows how
to create a simple web application (a newsfeed aggregator)
with a pluggable persistence layer. I used the tried
and true DAO pattern to hide the database access
mechanism from the rest of the application.
I implemented the DAO interface with both Hibernate
and Castor.
I did this to learn:
- What are the drawbacks of hiding powerful persistence
engine behind a simple DAO interface. What do you loose?
Will long transaction support work? What about lazy loading?
- What are the differences between and strenghts/weaknesses
of Castor and Hibernate?
- What is the best way to implement DAO with each of
the tools.
The code is very simple and (I hope) easy to follow,
so if you have a chance please take a look. Look at the
HibeAggregatorDAO and CastorAggregatorDAO implementations
to see how I used Hiberate and Castor to implement the
very same DAO. I'd love to get your opinions on the
above topics.
The readme is here:
http://sourceforge.net/project/shownotes.php?release_id=125110
The download is here:
http://sourceforge.net/project/showfiles.php?group_id=47722
Thanks,
- Dave
http://www.rollerweblogger.org/page/roller
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
- Re: [castor-dev] Castor vs. Hibernate example Dave Johnson
- Re: [castor-dev] Castor vs. Hibernate example Bruce Snyder
- Re: [castor-dev] Castor vs. Hibernate example Dave Johnson
- Re: [castor-dev] Castor vs. Hibernate example [Virusch... Patric Bechtel
