This is a repost with a better subject, hoping to get a hint.
I build a custom QueryCustomizer implementation to restrict the retrieved values of a collection to a known primary key.
I saw that I could add attributes at the deployment descriptor but the value of the
primary key changes dynamically during my application.
My sample:
public Query customizeQuery(Object anObject, PersistenceBroker aBroker, CollectionDescriptor aCod, QueryByCriteria aQuery)
{
aQuery.getCriteria().addEqualTo("field","value");
return aQuery;
}
The "value" should change dynamically. Is there really no way to pass additional dynamic arguments to the implementation?
IA Simple workaround is to use System properties but of course this just a hack for a test case. It's not thread save, it's slow
etc.
I found no way to find out where the current query came from to build sonething like a callback. Extending the Query implementation by
a user object would be a solution buit this modification shouldn't be done without consulting the OJB crew.
Implementing a user object might be difficult because the querry which is passed to the QueryCustomizer is generated by OJB and is
not directly coming from my code. So a modified Query would mean that the user object must be passed around by OJB Broker.
I still think that I miss something.
best regards,
Guido
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
