When using jOOQ with Nashorn, there may be a couple of interoperability issues related to overloading and varargs, as documented here:
http://blog.jooq.org/2014/09/19/learn-how-nashorn-prevents-effective-api-evolution-on-a-new-level

In short, when there are two methods like these:

interface SelectFromStep {
    SelectWhereStep from(String);
    SelectWhereStep from(TableLike<?>...);
}

... then, Nashorn will try to coerce argument types to string via JavaScript's ToString() function, before considering variable arity methods. I.e. the following call will result in calling from(String):

DSL.using(configuration)
   .select(...)
   .from(GENERATED_TABLE_REFERENCE);

While the linked blog post shows a couple of workarounds at the call-site, it would probably be more user-friendly to circumvent this issue by also providing a non-varargs, single-argument method that takes tables:

interface SelectFromStep {
    SelectWhereStep from(String);
    SelectWhereStep from(TableLike<?>);
    SelectWhereStep from(TableLike<?>...);
}

This should be applied throughout the API, where this can be done backwards-compatibly according to jOOQ's understanding of sematic versioning