>> The unit-vs-integration-test debate is a religious one... I can see >> how you don't want to go down the integration-test path... > > > My opinion is that I know better what I need than some framework someone > else designed and that frameworks should help me solve problems in the way I > feel best rather than limiting my options without a good reason. > > In this case here, I would like to hear "I'll support some form of > dependency injection in jOOQ 3.0". You already pass Configuration almost > everywhere, it wouldn't be a huge change to let it create all instances > (instead of just a few of them). > > The current situation is frustrating. jOOQ almost does what I need but > often, there is just a final / package private that prevents me from solving > my problem. Instead of investing 5-10 minutes to solve a trivial problem, I > have to spend a couple of days.
There's this point of view here... (1) > I can see how this design makes your life easier :-) But for me, your API > feels ... hostile. I hope you understand. > > I could maintain my own branch but it's effort I would like to avoid. > Especially when we talk about a "little" patch that adds DI to jOOQ - that > would be a huge beast and it would break for every release that you do. ... and then, there's this one. (2) (1) seems to claim that things should open up and be accessible, extendable, public, etc. (2) seems to claim that things should remain stable My mental Prolog processor goes mad at these claims. ;-) jOOQ's model is quite clear. What's in org.jooq follows semantic versioning (major / minor releases, API guarantees, stability, support). If you touch org.jooq.impl, however, then you're on your own. I think this model has made it possible to achieve anything at all. If you have any more concrete suggestions than "adding some form" of dependency injection", I'll be more than happy to discuss them. >From the information you have disclosed so far, I'm still not quite sure where jOOQ goes wrong -- 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.
