ess logic and back. I had to
kill the writer in order to use the
'acceptChanges()'
method. Does the default RowSetWriter handle
updating multiple tables?
Jerry
-Original Message-
From: John Bigboote [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 2:23 PM
To: Str
les?
>
> Jerry
>
> > -Original Message-
> > From: John Bigboote [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, November 26, 2002 2:23 PM
> > To: Struts Users Mailing List
> > Subject: Re: [OT] Updating CachedRowSet
> >
> >
> >
tiple tables?
Jerry
-Original Message-
From: John Bigboote [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 2:23 PM
To: Struts Users Mailing List
Subject: Re: [OT] Updating CachedRowSet
--- Jerry Jalenak <[EMAIL PROTECTED]> wrote:
[...snip...]
crs.updateString("userI
t; To: Struts Users Mailing List
> Subject: Re: [OT] Updating CachedRowSet
>
>
>
> --- Jerry Jalenak <[EMAIL PROTECTED]> wrote:
> >
> [...snip...]
> >
> >
> > crs.updateString("userInfo", userInfo);
> > crs.updateRow();
> >
--- Jerry Jalenak <[EMAIL PROTECTED]> wrote:
>
[...snip...]
>
>
> crs.updateString("userInfo", userInfo);
> crs.updateRow();
> crs.setWriter(null); // kill default writer
> crs.acceptChanges();
>
Why are you setting the writer to null? It's the
RowSetWriter that pr
Sorry I don't know how to fix your problem but I do have some comments. It
looks like your DAO class has a bunch of static methods. It's better to
have your DAOs be singletons and be created with a DaoFactory. This allows
various DAO implementations to be plugged in later. You lose this bene
6 matches
Mail list logo