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
Matcher strategies
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
Using custom matcher strategies
In the previous section, we have seen how to override generator strategies programmatically. In this chapter, we'll see how such strategies can be configured in the XML or Maven code generator configuration. Instead of specifying a strategy name, you can also specify a <matchers/> element as explained in the following subsections.
The generic structure of such matchers looks as follows:
<configuration>
<!-- These properties can be added directly to the generator element: -->
<generator>
<strategy>
<matchers>
<tables>
<table>
<!-- Match unqualified or qualified table names. If left empty, this matcher applies to all tables. -->
<expression>MY_TABLE</expression>
<!-- These elements influence the naming of a generated org.jooq.Table object. -->
<tableClass> a MatcherRule specification </tableClass>
<tableIdentifier> a MatcherRule specification </tableIdentifier>
<tableImplements>com.example.MyOptionalCustomInterface</tableImplements>
</table>
</tables>
</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()
.withTables(
new MatchersTableType()
// Match unqualified or qualified table names. If left empty, this matcher applies to all tables.
.withExpression("MY_TABLE")
// These elements influence the naming of a generated org.jooq.Table object.
.withTableClass(MatcherRule. a MatcherRule specification )
.withTableIdentifier(MatcherRule. a MatcherRule specification )
.withTableImplements("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 {
tables {
table {
// Match unqualified or qualified table names. If left empty, this matcher applies to all tables.
expression = "MY_TABLE"
// These elements influence the naming of a generated org.jooq.Table object.
tableClass = " a MatcherRule specification "
tableIdentifier = " a MatcherRule specification "
tableImplements = "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.
A matcher configuration element can be any of these things:
- A regular expression matching an identifier
- A
org.jooq.meta.jaxb.MatcherRulespecification (see MatcherRule) - A constant value
All regular expressions that match object identifiers try to match identifiers first by unqualified name (org.jooq.meta.Definition.getName()), then by qualified name (org.jooq.meta.Definition.getQualifiedName()).
The following sections explain the above more in detail:
Table of contents
- 5.6.1.
- MatcherRule
- 5.6.2.
- Matching schemas
- 5.6.3.
- Matching tables
- 5.6.4.
- Matching fields
- 5.6.5.
- Matching routines
- 5.6.6.
- Matching sequences
- 5.6.7.
- Matching enums
- 5.6.8.
- Matcher examples
| previous : next |
References to this page
Feedback
Do you have any feedback about this page? We'd love to hear it!