I'm not only new to OJB, but new to Ant and building (I've been in the interpreted throw-away scripting world for a long time), so part of what I need to learn stems from my ignorence there. After I downloaded OJB and expanded everything, I followed the instructions at platforms.html to set up a test database. I "switched on" the line for the MySQL profile. I also edited the mysql.profile with the proper jdbc url info, username, password, etc. I understood that two things were happening at once: 1) the build process was creating the necessary OJB internal tables, not all of which (or any necessarily?) are required; and 2) the build process was creating and populating tables for the example database, which simulates an actual production db.
Here are my questions:
When I want to use OJB to connect to my own production db, do I need to run the build again, against a new build.xml file; or is it already set up to use MySQL, and I only have to alter a few configuration files for the new jdbc url, password, etc?
The file repository_database.xml contains a jdbc-connection-descriptor with attributes like jcd-alias="@JCD_ALIAS@" I'm not familiar with @foo@ notation--does this mean there is supposed to be a previously-defined value for some JCD_ALIAS token or entity? Or is this a placeholder that I should replace with real values?
Also, what is the relationship between the repository_database.xml file and the values I set in mysql.profile before the build? Is the build supposed to write this XML file out?
If I need to rerun the build, how do I avoid creating all the example tables?
I apologize for the newbie questions. I'm climbing a steep learning curve, and I'm probably not being as patient as I should be. Help me out, and I promise I'll find much more interesting questions soon enough.
Best Regards,
Michael
||
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
