Yes, write access is controlled by the DB, but the user has full access and
the app was writin' until I changed out the connection.
In fact, when I revert back to the Struts BasicDataSource it works without
a problem -- very peculiar.
I switched over to the JNDI connection because I created a small plugin to
get my 20+ lookup tables into application context on startup for drop-down
lists and whatnot (which seems to works well). I did this because I
couldn't figure out how to get a datasource reference in the plugin. If I
could get a reference in the plugin I could just revert back to the
BasicDataSource. Similarly, if you are using a DAO pattern with the DAO
performing custom create, read, update, delete --- are struts users
generally passing a connection from the action to the DAO or is the DAO
grabbing a connection from a seperate plugin or servlet or connection
factory or JNDI or somewhere else?
-- thanks Doug
"Craig R.
McClanahan" To: Struts Users Mailing List
<[EMAIL PROTECTED] <[EMAIL PROTECTED]>
he.org> cc:
Subject: Re: DB Write Access Problem with
Tomcat JNDI
07/29/2003
04:11 PM
Please respond
to "Struts
Users Mailing
List"
On Tue, 29 Jul 2003 [EMAIL PROTECTED] wrote:
> Date: Tue, 29 Jul 2003 14:21:47 -0700
> From: [EMAIL PROTECTED]
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: DB Write Access Problem with Tomcat JNDI
>
> Has anyone run into a problem with acquiring write access to a db using
the
> jndi setup with tomcat 4.1.24.
Isn't write access to the various tables controlled by what roles the
Oracle username you specify has?
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
