Resin DB-pooling + authentication. HELP!

[Philippe Desrosiers]

I need to use Connection pooling with a MySQL database for my web application under Resin-3.1.0.

Here's what I've got so far:

in resin.conf:

    < !-- Database pool -->
    <database>
        <jndi-name>jdbc/mydb</jndi-name>
        <driver type="com.mysql.jdbc.Driver">
            <url>jdbc:mysql://mysqlserver/mydb</url>
            <user>username</user>
            <password>password</password>
        </driver>
        <prepared-statement-cache-size>0</prepared-statement-cache-size>
        <max-connections>100</max-connections>
        <max-idle-time>30s</max-idle-time>
    </database>

In the web.xml for my app:

<!-- refers to the datasource defined in resin.conf -->
    <resource-ref>
        <description>DB Connection Pooling</description>
        <res-ref-name>jdbc/mydb</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>
    <authenticator
        type='com.caucho.server.security.JdbcAuthenticator'>
        <init>
            <logout-on-session-timeout>true</logout-on-session-timeout>
            <data-source>jdbc/mydb</data-source>
            <password-query>
                SELECT password FROM USERS WHERE login=?
            </password-query>
            <role-query>
                SELECT role FROM USER_ROLES WHERE login=?
            </role-query>
        </init>
    </authenticator>

Of course, <authenticator> is a special resin tag, so I have to change the schema of my web.xml file to use resin's special schema. Once that's done, the resource-ref element is no longer recognized.

How the F*** do I set up resin to use JDBC authentication with a connection pool? This was so simple using Tomcat.

Please, before anyone starts spouting "read the documentation" comments, rest assured I've spent the last 24 hours reading the bloody documents, and they don't help.
[ June 22, 2007: Message edited by: Philippe Desrosiers ]

[Philippe Desrosiers]

Okay, I finally gave up, and created a seperate <database> element in my web.xml. Now, for some reason, authentication always fails, but there's no information in the log file. I can't even tell if Resin is connecting to the database correctly, or what the problem could be. The request just gets forwarded to the uri specified in the <form-error-page> tag.

In web.xml:

    <database>
        <jndi-name>jdbc/userdb</jndi-name>
        <driver type="com.mysql.jdbc.Driver">
            <url>jdbc:mysql://mysqlserver/mydb</url>
            <user>username</user>
            <password>password</password>
        </driver>
        <prepared-statement-cache-size>0</prepared-statement-cache-size>
        <max-connections>100</max-connections>
        <max-idle-time>30s</max-idle-time>
    </database>
 
    <security-constraint>
        <web-resource-collection>
            <web-resource-name>Admin Portal</web-resource-name>
            <url-pattern>/admin/*</url-pattern>
        </web-resource-collection>
        <auth-constraint>
            <role-name>user</role-name>
        </auth-constraint>
    </security-constraint>
 
    <!-- Resin-specific JdbcAuthenticator -->
    <authenticator
        type='com.caucho.server.security.JdbcAuthenticator'>
        <init>
            <logout-on-session-timeout>true</logout-on-session-timeout>
            <data-source>jdbc/userdb</data-source>
            <password-query>
                SELECT password FROM USERS WHERE login=?
            </password-query>
            <role-query>
                SELECT role FROM USER_ROLES WHERE login=?
            </role-query>
        </init>
    </authenticator>
 
    <login-config>
        <auth-method>FORM</auth-method>
        <realm-name>Admin Portal</realm-name>
        <form-login-config>
            <form-login-page>/login.jsp</form-login-page>
            <form-error-page>/login.jsp?err=true</form-error-page>
        </form-login-config>
    </login-config>

No java exceptions are thrown, and I triple-checked that the required role ('user') and user ('admin') exist...
[ June 22, 2007: Message edited by: Philippe Desrosiers ]