Hi Steve, I'm sorry for the late reply. I just came back from vacation and I wasn't able to access Internet frequently during the last 4 weeks.
> I am a new user of jooq and there have been several cases where I am not > able to access methods and classes. Can someone comment on the > public/private policy and the potential for making more things public? The policy is described here: http://www.jooq.org/manual/JOOQ/ In the original design, only the Factory should be exposed from the implementation package. All other "impl" classes are public due to the limitations of package visibility of the Java language - i.e. generated code being part of jOOQ's "internals" should be able to access the "impl" classes. > In my case, I'd like to see TableFieldImpl become public (so I can derive > it). That seems like a bad idea at first. These "impl" classes change frequently between releases, and I wouldn't like to see them being part of the public API. What extensions do you need? > I'm also trying to do several things in an ExecuteListeners and it > would be nice to see InsertQuery.getInto() move into the Interface and make > public. That probably makes sense. I filed this as feature request #1492: https://sourceforge.net/apps/trac/jooq/ticket/1492 I'll see what other internals can be exposed in the public non-DSL API > In case anyone wants to know, I'd like to be able to detect my derived class > of TableFieldImpl in the execute listener so that I can do some additional > things that make sense for my derived field. Could you explain this a bit more? Maybe there is another solution, not involving API changes? Cheers Lukas
