Dominik, that worked! Champion!!! My revised context.xml looks like this: <Context path="/mind" docBase="D:/Development/Projects/mind/src/webapp" debug="99" reloadable="true"> <Resource name="jdbc/MindDB" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="mind" password="*******" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost/mind"/>
<Realm className="org.apache.catalina.realm.DataSourceRealm" debug="99" dataSourceName="jdbc/MindDB" localDataSource="true" userTable="mind_user" userNameCol="alias" userCredCol="password" userRoleTable="mind_user_role" roleNameCol="name"/> </Context> On Mon, 07 Feb 2005 08:57:08 +0100, Dominik Drzewiecki <[EMAIL PROTECTED]> wrote: > Dan Washusen <[EMAIL PROTECTED]> wrote: > > Hi Sven, > > I can access the data source from within my code using the name > > "java:/comp/env/jdbc/MindDB" and everything works great. It's just > > that the Realm can't... I have found a few other posts to this list > > with the same problem and one of the email suggested that the Realm is > > configured before the DataSource causing an error to be thrown during > > realm initialisation (as the DataSource is missing). > > > > It looks like the "solution" is to move the DataSource configuration > > to the Global configuration area or to use the JBDCRealm. > > It is not necessary to make the datasource global. Try adding > localDataSource="true" to your context Realm definition. > Having consulted the docs for 4.1.x, 5.0.x and 5.5.x, t seems that this > flag is only allowed in the latest version of tomcat. There's a chance > though that it has been backported without having the docs updated. > > HTH, > /dd > > -- Jar-Jar makes the Ewoks look like f*%#ing Shaft! - Tim Bisley --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]