Hi Guido, > Hi, > > I am new with the JDO OJB implementation. > I took a closer look on the tutorial4 implementation. > The tutorial4.jdo looks very small.
Yes, it contains only one class description for the Product class of the tutorial app. > Is the JDO api > using the repository.xml to get the reference description? which reference description? currently the Jdbc-Connection description is taken from repository.xml because. The JDORI enhancer does not accept the <extension vendor-name="ojb" key="dbplatform" value="hsqldb"/> <extension vendor-name="ojb" key="dbjdbc-level" value="2.0"/> <extension vendor-name="ojb" key="dbdriver" value="org.hsqldb.jdbcDriver"/> <extension vendor-name="ojb" key="dbprotocol" value="jdbc"/> <extension vendor-name="ojb" key="dbsubprotocol" value="hsqldb"/> <extension vendor-name="ojb" key="dbalias" value="../OJB"/> <extension vendor-name="ojb" key="dbusername" value="sa"/> <extension vendor-name="ojb" key="dbpassword" value=""/> on the JDO level. Altough it is compliant with the jdo.dtd !!! We also take the mapping for the OJB internal tables from the original repository.xml. So only user tables need to be declared in the jdo file. > Is the reference enhancer used by OJB tutorial4? It's not required, but you can enhance the Product class by: 1. get jdori.jar from the sun JDO site 2. place jdori,jar into the ojb/lib directory 3. run the "enhance" target from our build.xml ant script cheers, Thomas > best regards, > > Guido > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
