Hi, I tried exactly what you descibed here. OJB seems to look at the default (OJB) database and not on my user database. Maybe this is a nes issue.
I couldn find information about the in memory OJB tables. Could you give me a better link to look at? cheers, Guido ----- Original Message ----- From: "Armin Waibel" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Tuesday, January 28, 2003 11:28 AM Subject: Re: Multiple database problem > Hi Guido, > > ----- Original Message ----- > From: "Guido Beutler" <[EMAIL PROTECTED]> > To: "OJB Users List" <[EMAIL PROTECTED]> > Sent: Tuesday, January 28, 2003 7:03 AM > Subject: Re: Multiple database problem > > > > Hi, > > > > I am evaluating OJB for a project. Maybe that the decision will be to > use a > > other persistence layer than OJB so I do not want to create the OJB > > tables at the normal production database. > >It is easier to drop the > > whole OJB database than to delete all the OJB tables by hand. > > Currently I would like to use OJB for bean managed persistence with > > jboss but I started with a small sample running under junit. > > > > Is there a way to get it working with 0.9.8 ? If I could build > > some tests and OJB will be used at that project in future > > I do not have a problem to create OJB Tables at the production > > enviroment. > > OK, now I have a better understanding;-) > To make it work with 0.9.8 you could try the following: > - define the repositoryOJB.xml as default (set in OJB.properties) > -separate the class-descriptors in a repositoryProd_user.xml file using > a 'ENTITY link' in repositoryProd.xml. > - let the default repository know about all used class-descriptors > (use entity link to the repositoryProd_user.xml) > > It's also possible to run OJB without any intern table > (see faq in shipped docs, e.g PB-api + InMemorySequenceManager). > > > > > What is the difference with an EJB server enviroment? > > Can I use the transaction layer of jboss, if yes how? > Yes, you could use OJB with container-managed-tx and > bean-managed-tx. > (OJB was shipped with working bean examples using cm-tx, > see src/ejb/org/apache/ojb/ejb). > see section 'deployment' in the shipped docs for jboss integration. > see build-xdoclet.xml to generate the sample beans. > > regards, > Armin > > > > > cheers, > > > > Guido > > > > > > > > ----- Original Message ----- > > From: "Armin Waibel" <[EMAIL PROTECTED]> > > To: "OJB Users List" <[EMAIL PROTECTED]> > > Sent: Tuesday, January 28, 2003 2:21 AM > > Subject: Re: Multiple database problem > > > > > > > Hi Guido, > > > > > > ----- Original Message ----- > > > From: "Guido Beutler" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Monday, January 27, 2003 8:14 PM > > > Subject: Multiple database problem > > > > > > > > > > Hello, > > > > > > > > I tried to separate the OJB internal tables from existing (user > data) > > > > tables. > > > You separate internal tables in one database and user data in > another > > > database? > > > If so, I advise not to do that, because OJB does not support > > > distributed transaction out of the box (or do you use a j2ee conform > > > application server?). > > > With next release this will be definitely not possible to do. Each > > > database has its own OJB intern tables (if necessary). > > > > > > regards, > > > Armin > > > > > > > I used the faraway sample and build different repository.xml and > > > > repository_user.xml. > > > > From the log I cansee that both jdbc connections work. > > > > I am executing a simple select but OJB reports that the table > could > > > not be > > > > found. > > > > Currently I think that I may have a configuration problem. > > > > Is there a way to get logging information for sql statements and > on > > > which > > > > connection (and database) the statement was executed by ojb? > > > > I think that my statement is executed against the OJB (the > default) > > > database > > > > and not against my user database. How can I verify that? > > > > > > > > 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]> > > > > > > > > > -- > > 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]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>