17, 2003 5:30 PM
To: Struts Users Mailing List
Subject: RE: DAO and Struts Best Practice
I have read the official DAO pattern on the Sun's website. WOW! Good stuff.
If you don't understand it that is a good place to start. Is there anyone
using the strict DAO Abstract Factory Pattern? Yes
, 2003 6:03 AM
To: 'Struts Users Mailing List'
Subject: RE: DAO and Struts Best Practice
I'm using it and it seems to work pretty well. However, on my last project,
I used such things like UserDAOMySQL, and it seems like it would be a real
pain (right now) to write a bunch of new classes for Oracle
/viewcvs.cgi/struts/struts-resume/
Or download it here:
http://raibledesigns.com/struts
HTH,
Matt
-Original Message-
From: Brandon Goodin [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 20, 2003 7:01 AM
To: Struts Users Mailing List
Subject: RE: DAO and Struts Best Practice
That's
I've actually never heard of DAO's described that way. I'm more
familiar with terms like Table Gateway and Row Gateway patterns for
DAO. If you are looking at using BeanUtils, then you want to look at
creating a Row Gateway where you have beans that are Gateways to a
single row, or only describe
[mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 9:31 AM
To: 'Struts Users Mailing List'
Subject: RE: DAO and Struts Best Practice
I've actually never heard of DAO's described that way. I'm more
familiar with terms like Table Gateway and Row Gateway patterns for
DAO. If you are looking
I TOO am too dense to communicate it clearly sometimes:
But this is clear:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/ROOT/src/basicWebLib/org/commons/DAO
Take a look at the DAO interface; and then a DAO implementation above.
(OT: The 2nd DAO implementation there will be using
So when you are describing objects that receive parameters, you are
looking along the lines of a transaction? If so, you usually want to
interface out the transaction object so you can possibly change the
language later-- take a look at OJB for example. They have the base
persistence broker
List'
Subject: RE: DAO and Struts Best Practice
So when you are describing objects that receive parameters, you are
looking along the lines of a transaction? If so, you usually want to
interface out the transaction object so you can possibly change the
language later-- take a look at OJB
Hello all.
I've looked at a lot of DAO based projects and I haven't yet found one that I
really like. My problem is that often I end up having to access similiar data
from very different sources. For example, my current project needs to be able
to gather the same data via JDBC, JMS, or static
PROTECTED]]
Sent: Friday, January 17, 2003 1:45 PM
To: [EMAIL PROTECTED]
Subject: RE: DAO and Struts Best Practice
Hello all.
I've looked at a lot of DAO based projects and I haven't yet found one that
I
really like. My problem is that often I end up having to access similiar
data
from very
On Fri, 17 Jan 2003 13:59:34 -0600 Jacob Hookom [EMAIL PROTECTED] wrote:
You might want to look at Castor for XML/JDBC
The simplest solution is to write an intermediate layer. Struts calls
specialized methods on this layer to handle calls to multiple persistence
services, invisible to your
PROTECTED]
Subject: RE: DAO and Struts Best Practice
Hello all.
I've looked at a lot of DAO based projects and I haven't yet found one that
I
really like. My problem is that often I end up having to access similiar
data
from very different sources. For example, my current project needs to be
able
12 matches
Mail list logo
