Hi Lukas,
> > I bet you will try to argue against this convenience. > > jOOQ always overloads methods for tedious repetitive tasks. > For me, it was important to understand what the ConnectionProvider is and what it is not. All the rest, including this explicit distinction between safe and unsafe was or was not relevant depending on that. > > Anyway, this leads to a real dumb ConnectionProvider implementation > > that just delegates everything to Weblogic. > ConnectionProvider is an adapter to whatever mechanism the user prefers, needed for JOOQ to handle Connections, DataSources or whatever custom mechanisms behind a minimalistic contract. It is not meant to be a reliable factory that tools can use (which is the aspect I wanted to clear). > > - There are convenience methods to register "global" ExecuteListeners, > > which are wrapped in a DefaultExecuteListenerProvider > DebugListener will remain stateless by retaining data in the context. The reason is that users can easily configure a DebugListener but not a Provider, if I were to use that mechanism instead. Anyway, the contract on the data map placed in the context is now much better than before (per execution that is). > Last-minute feedback before RC3 is welcome ;-) > Welcome RC3! If not, I think the current ExecuteListenerProvider will more or less > match your expectations. It is indeed a good solution to allow for > injecting stateless / stateful ExecuteListeners into jOOQ without jOOQ > noticing. > Yes, for internal use (by JOOQ users that is), it is a good fit. For a generic listener that is meant to be distributed to users, better rely on the data map to retain states. > I don't agree with all of this, as you know :-) > It is only a matter of context. What you say is true considering the behavior is managed externally to the library. The question I was raising was whether it should be somewhat managed to allow for additional tools to work (which was what I believed ConnectionProvider was doing the first time I saw it). Keep up the good work! Cheers, -Christopher -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
