I have this in my OJB.properties file:
repositoryFile=repository.xml
I purposely put some jibberish in the repository.xml file earlier on and I did indeed get an exception indicating that there was a problem reading the file. Based on this, I am assuming that the file is accessible and is being read.
I also know that the repository.xml file is valid because when I run my test cases inside Eclipse, I'm able to insert/update/select/delete from the database using the default connection.
It's very odd, but I'm thinking that there is a bug somewhere in the OJB code that loads the file. I started poking around the source earlier on and will try to get into it more later.
If you have more ideas, I'd love to hear them and try them out.
I just tried a very simple servlet that uses PB-Api with OJB, Tomcat 4.1.18, JDK 1.4.2 on WinXP, and it works. One thing I stumbled upon was that I forgot to put the repository.dtd into the classes folder. Since OJB parses XML files with validation turned on, this lead to an error in the XML parser. This is the layout that worked for me:
\<webappname>
\WEB-INF
web.xml
\classes
<servlet classes>
OJB.properties
repository.dtd
repository.xml
repository_user.dtd
repository_database.dtdThe connection descriptor is:
<jdbc-connection-descriptor
jcd-alias="default"
default-connection="true"
platform="MySQL"
jdbc-level="3.0"
driver="com.mysql.jdbc.Driver"
protocol="jdbc"
subprotocol="mysql"
dbalias="//localhost/test"
username="***"
password="***"
eager-release="false"
batch-mode="false"
useAutoCommit="1"
ignoreAutoCommitExceptions="false"
/>
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
