hi again, [EMAIL PROTECTED] wrote:
ok, but isn't it a lot of work to create all the interfaces and proxies? you need 2 classes and one interface for every proxy implementation, or am i wrong?If you use the OJB dynamic proxy feature you only have to write a interface for yor entity class. OJB generates the proxy class dynamically.
just set proxy="true" in repository.xml
cheers,
Thomas
juergenHi Juergen, we are using proxies in single mode. This works fine. We wrote our own models for swing-components using proxies, so only the shown objects will be materialized. The performance is ok. regards Axelhi!
i want to display several lists (collections of the same class). the user chooses one of the objects, and this will be loaded from the database.
my current solution is a PB.getCollectionByQuery, but this is very slow, because the whole object tree is loaded (but not used). is there a solution?
i'm not sure, but i think this should be done by using proxy classes, but i had lots of troubles with them in client / server mode (never tried them in singlevm).
please help
juergen
--
To unsubscribe, e-mail: <mailto:ojb-user-> [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]>