WHIRLYCOTT wrote:
Yes, I have the repository.dtd in my WEB-INF/classes dir as well. I'm using that in Eclipse to validate my repository.xml file.
One difference is that I'm using Tomcat 5.0.18. Would you mind repeating your experiment using a version of Tomcat 5?
I'm trying to figure out what I know at this point:
1) when working on the command line, I can use my OJB.properties and repository.xml file just fine (and can pass 12 junit tests against my database)
2) when running inside Tomcat, OJB.properties is being read
3) when running inside Tomcat, repository.xml is being read
4) the error message that OJB is giving is either incorrect or not very useful
If you can try your test out in Tomcat 5, I'd love to know if that makes a difference.
Mhmm, don't know whether I be able to do so today, but I'll try. Have you tried a 4.1.x Tomcat ?
Since you're using Eclipse, you could also debug OJB+Tomcat. So try the following:
1. Install and configure the Sysdeo Tomcat plugin if you haven't done so already
2. Using the OJB source dist or (preferably) a CVS checkout, build OJB with 'ant jar-debug'. This builds a debug version which can be used to debug.
3. Import the Eclipse workspace that comes with OJB
4. Put a breakpoint at the beginning of org.apache.ojb.broker.metadata.RepositoryPersistor#readMetadataFromXML(InputSource, Class)
5. Deploy your project into Tomcat and start Tomcat using the Sysdeo Tomcat (which automatically starts Tomcat in debug mode and connects to it)
Now you can step through the loading of the repository.xml.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
