I am using OJB under JBoss (managed transaction) front-ended by a service session bean and I am trying to optimize the number of queries needed to materialize my objects. I have several objects with several relationships among them and whenever I materialize one of them (say a person object), OJB queries for the rest of them. Things I tried: collection proxies: I see SELECT count(*) from TABLE_A.... but I also see Select field1, field2... from TABLE_A (I assume is materializing those objects). If I turn off the transaction requirement, I get an exception because OJB cannot find a transaction.
I have tried proxies in a standalone app (basically, copied my objects from the web project into a standalone project) and tried SELECTing the same object (person) without a transaction, OJB performs less queries.. Whenever I don't use a transaction in the standalone program, the collection proxies do work as intended (just SELECTing count(*) ). Are there any pointers (tips, help) that I can use for minimizing the number of queries needed to materialize objects. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
