Thanks Alex for your response. I am trying to understand this. I have downloaded juddi-distro-3.1.5.zip. >From this distribution I have extracted juddiv3.war from the bin directory and >deployed it. This resulted in my initial error. The guide for the database connection setup states that "By default jUDDI uses an embedded Derby database. This allows us to build a downloadable distribution that works out-of-the-box, without having to do any database setup work." Does this mean that I did something wrong in the deployment? Should I be able to get juddi up and running (using Derby) in an existing development environment that already uses Tomcat? If so, I think that should be my first step and after that I should try to switch database connection.
Following the guide for the database connection setup: 1. edit persistence.xml. In the juddiv3.war it is the OpenJPA version. In the oracle section the hibernate version is mentioned. Should I replace the one in the juddiv3.war and use the Hibernate version? 2a. define datasource in context.xml. There is no context.xml in the juddiv3.war. Do I need to copy it myself to the directory <tomcat>/juddiv3/META-INF/ directory? 2b. There are some context.xml examples for MySql, Postgress, but not for Oracle. Do you have an example for Oracle? 3. add the database specific driver to your classpath. What is the classpath in a Tomcat environment? Where do I have to put the file? 4. I assume I have to create the database juddiv3 as well? With your answers I will try to get a successful implementation with an Oracle backend and update the oracle installation guide. Thanks, Arnold This message is subject to the following E-mail Disclaimer. (http://www.crv4all.com/disclaimer-email/) CRV Holding B.V. seats according to the articles of association in Arnhem, Dutch trade number 09125050.