ScanTopDown: This boolean property
controls whether Kodo looks for metadata files top-down
in the package tree. Kodo defaults to bottom-up
scanning, meaning that when scanning for metadata for
class C, Kodo looks first for
C.jdo, then package.jdo
in C's package, then
package.jdo in the parent package,
and so forth to the package root.

JPA has built-in settings for listing your persistent classes, which
the JPA Overview
describes. Kodo supports these JPA standard settings by translating
them into its own internal metadata factory settings.
The standard metadata factories all accept the following properties for
locating persistent classes. Each property represents a different
mechanism for locating persistent types; you can choose the mechanism or
combination of mechanisms that are most convenient. See
Section 5.1, “Persistent Class List” for a discussion of when it
is necessary to list your persistent classes.

Resources: A semicolon-separated list of
resource paths to metadata files or jar archives.
Each jar archive will be scanned for
annotated JPA entitiesorJDO metadata files
based on your metadata factory.

URLs: A semicolon-separated list of URLs
of metadata files or jar archives.
Each jar archive will be scanned for
annotated JPA entitiesorJDO metadata files
based on your metadata factory.

ClasspathScan: A semicolon-separated list of
directories or jar archives listed in your classpath.
Each directory and jar archive will be scanned for
annotated JPA entitiesorJDO metadata files
based on your metadata factory.