Available in versions: Dev (3.20) | Latest (3.19) | 3.18 | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11 | 3.10
Matching routines
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
The following example shows how to define a MatcherStrategy for generated org.jooq.Routine types and related objects:
<configuration>
<!-- These properties can be added directly to the generator element: -->
<generator>
<strategy>
<matchers>
<!-- Specify 0..n routine matchers to provide a strategy for naming objects created from routines. -->
<routines>
<routine>
<!-- Match unqualified or qualified routine names. If left empty, this matcher applies to all routines. -->
<expression>MY_ROUTINE</expression>
<!-- These elements influence the naming of a generated org.jooq.Routine object. -->
<routineClass> a MatcherRule specification </routineClass>
<routineMethod> a MatcherRule specification </routineMethod>
<routineExtends>com.example.MyOptionalRoutineBaseType</routineExtends>
<routineImplements>com.example.MyOptionalCustomInterface</routineImplements>
</routine>
</routines>
</matchers>
</strategy>
</generator>
</configuration>
See the configuration XSD, standalone code generation, and maven code generation for more details.
new org.jooq.meta.jaxb.Configuration()
// These properties can be added directly to the generator element:
.withGenerator(new Generator()
.withStrategy(new Strategy()
.withMatchers(new Matchers()
// Specify 0..n routine matchers to provide a strategy for naming objects created from routines.
.withRoutines(
new MatchersRoutineType()
// Match unqualified or qualified routine names. If left empty, this matcher applies to all routines.
.withExpression("MY_ROUTINE")
// These elements influence the naming of a generated org.jooq.Routine object.
.withRoutineClass(MatcherRule. a MatcherRule specification )
.withRoutineMethod(MatcherRule. a MatcherRule specification )
.withRoutineExtends("com.example.MyOptionalRoutineBaseType")
.withRoutineImplements("com.example.MyOptionalCustomInterface")
)
)
)
)
See the configuration XSD and programmatic code generation for more details.
// The jOOQ-codegen-gradle plugin has been introduced in version 3.19 only.
// The jOOQ-codegen-gradle plugin has been introduced in version 3.19 only.
generationTool {
// These properties can be added directly to the generator element:
generator {
strategy {
matchers {
// Specify 0..n routine matchers to provide a strategy for naming objects created from routines.
routines {
routine {
// Match unqualified or qualified routine names. If left empty, this matcher applies to all routines.
expression = "MY_ROUTINE"
// These elements influence the naming of a generated org.jooq.Routine object.
routineClass = " a MatcherRule specification "
routineMethod = " a MatcherRule specification "
routineExtends = "com.example.MyOptionalRoutineBaseType"
routineImplements = "com.example.MyOptionalCustomInterface"
}
}
}
}
}
}
See the configuration XSD and gradle code generation for more details.
As always, when regular expressions are used, they are regular expressions with default flags.
When using anyroutineExtends, etc. setting, you must make sure to correctly implement the internal jOOQ APIs, which are not documented here for they are internal. In particular, if you're extendingorg.jooq.impl.TableImpl, for example, your custom base class may break between minor versions of jOOQ, as new constructors are added.
See MatcherRule for more information about MatcherRule specifications.
Feedback
Do you have any feedback about this page? We'd love to hear it!