Hi,
JML (Brujula) wrote:
Thank you for your answer Alessandro, but it doesn't work with OSCache.
Anybody has another solution?
Why doesn't it work with OSCache what's the problem?
Could you describe why you need to this access to cache in your method,
why you can't use broker.getObjectById
Hi Rick,
OJB Dev wrote:
Hello,
I am using OJB 1.0.3 and was wondering why it seems that the pool settings
have two different places to set the same settings. Would like to know which
one takes precedence, if any, and what is the proper/preferred method to
use.
This are different pools.
In O
Could you perhaps provide some more info, specifically the complete
class descriptor (or a comparative sample) and your usage of OJB for
storing and retrieving the object ?
Tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
While I'm not that familiar with the specifics of the pool, settings
in OJB.properties are usually system-wide, settings in the
repository.xml (jdbc-connection-descriptor or sub-element to be
precise) only for the database described by this connection
descriptor, and in some cases there are even se
Hello OJB-Users,
I have even started using OJB and so far all works fine :o) (1:1, 1:n...)
I would be pleased when you can help me with my first Problem.
I'm looking for an solution like 'Customizing collection queries'
descriped in the Guide 'advanced O/R technique' for 1:1 references.
A short
Thank you for your answer Alessandro, but it doesn't work with OSCache.
Anybody has another solution?
Alessandro Colantoni wrote:
you can do:
broker = ServiceLocator.getInstance().findBroker();
FieldDescriptor[] pkFields = broker.getClassDescriptor
(realClass).getPkFields();
String[] fieldName
