Well I'm a jUDDI "newbie" myself and had the same problem.  However, I was
able to fix my problem by updating tomcat's conf/context.xml file.  I added 
    <Resource name="jdbc/juddiDB" auth="Container"
              factory="org.apache.commons.dbcp.BasicDataSourceFactory"
              driverClassName="com.mysql.jdbc.Driver"
              url="jdbc:mysql://localhost:3306/juddi"
              maxActive="30"
              maxIdle="20000"
              username="root"
              password="mysql123"
              type="javax.sql.DataSource" >
    </Resource>

I'm assuming that your web.xml has a resource-ref entry something similar to
    <resource-ref>
        <description>juddi DB Connection</description>
        <res-ref-name>jdbc/juddiDB</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>

Moving the "Resource" entry from server.xml to context.xml seemed to to the
trick for me.

Good luck.

Mike



--
View this message in context: 
http://www.nabble.com/Deployed-jUDDI-with-Tomcat-5.5-t1303052.html#a3590944
Sent from the jUDDI - User forum at Nabble.com.

Reply via email to