Available in versions: Dev (3.19) | Latest (3.18) | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11 | 3.10 | 3.9
Matching fields
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
The following example shows how to define a MatcherStrategy for generated org.jooq.Field types and related objects:
<configuration>
<!-- These properties can be added directly to the generator element: -->
<generator>
<strategy>
<matchers>
<!-- Specify 0..n field matchers to provide a strategy for naming objects created from fields. -->
<fields>
<field>
<!-- Match unqualified or qualified field names. If left empty, this matcher applies to all fields. -->
<expression>MY_FIELD</expression>
<!-- These elements influence the naming of a generated org.jooq.Field object. -->
<fieldIdentifier> a MatcherRule specification </fieldIdentifier>
<fieldMember> a MatcherRule specification </fieldMember>
<fieldSetter> a MatcherRule specification </fieldSetter>
<fieldGetter> a MatcherRule specification </fieldGetter>
</field>
</fields>
</matchers>
</strategy>
</generator>
</configuration>
See the configuration XSD, standalone code generation, and maven code generation for more details.
new org.jooq.util.jaxb.Configuration()
// These properties can be added directly to the generator element:
.withGenerator(new Generator()
.withStrategy(new Strategy()
.withMatchers(new Matchers()
// Specify 0..n field matchers to provide a strategy for naming objects created from fields.
.withFields(
new MatchersFieldType()
// Match unqualified or qualified field names. If left empty, this matcher applies to all fields.
.withExpression("MY_FIELD")
// These elements influence the naming of a generated org.jooq.Field object.
.withFieldIdentifier(MatcherRule. a MatcherRule specification )
.withFieldMember(MatcherRule. a MatcherRule specification )
.withFieldSetter(MatcherRule. a MatcherRule specification )
.withFieldGetter(MatcherRule. a MatcherRule specification )
)
)
)
)
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 field matchers to provide a strategy for naming objects created from fields.
fields {
field {
// Match unqualified or qualified field names. If left empty, this matcher applies to all fields.
expression = "MY_FIELD"
// These elements influence the naming of a generated org.jooq.Field object.
fieldIdentifier = " a MatcherRule specification "
fieldMember = " a MatcherRule specification "
fieldSetter = " a MatcherRule specification "
fieldGetter = " a MatcherRule specification "
}
}
}
}
}
}
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.
See MatcherRule for more information about MatcherRule specifications.
Feedback
Do you have any feedback about this page? We'd love to hear it!