Hi Karl! I thought about some lifecycle event where you can register a callback before the query is executed. That should also cover other use cases. Agree that there should also be some more helpers then on the QueryInvocationContext, which is exposed to the callback.
On Sat, Jan 24, 2015 at 1:57 PM, Karl Kildén <[email protected]> wrote: > Hi Thomas! Thanks for your reply. Seems to me Map<String, String> would be > sufficient as a way to dynamically setup hints and then expose it in a > class with a marker (annotation / interface). Perhaps add it directly > in CdiQueryInvocationContext? > > cheers > > On 22 January 2015 at 10:17, Thomas Hug <[email protected]> wrote: > > > Hey Karl! > > Yes we keep identifying areas where an extension API would come in handy. > > Will propose something in JIRA. Not sure if it makes sense (yet) to think > > about adding provider specific modules if your stackoverflow question > hints > > that. Although we already do have provider specific code (e.g. query > string > > extraction from named queries). I'm currently really really bad in adding > > new stuff so patience and help is appreciated :-). > > > > On Wed, Jan 21, 2015 at 6:39 PM, [email protected] < > > [email protected]> wrote: > > > > > Hello! Basically I suspect this question of mine > > > > > > > > > http://stackoverflow.com/questions/28073430/jpa-eclipselink-global-batch-fetch > > > > > > To be left unresolved. Can the magics of data module help out somehow? > A > > > hook to inject hints or something? Cheers and thanks for data module > > > > > > Skickat från min iPhone > > >
