The documentation recommends to subclass org.atteo.classindex.processor.ClassIndexProcessor if you want to customize the ClassIndexProcessing. By setting custom Java-packages via org.atteo.classindex.processor.ClassIndexProcessor.indexPackages(String...) the processor generates jaxb.index files. Unlike the referenced jaxb-documentation
Fully qualified class names are not allowed. ...
the processor generates a fqcn for all classes in the package.
e.g. for package org.custom the jaxb.index-file contains class items like org.custom.Foobar instead of a simple relative classname Foobar.
While accessing the classNames via ClassIndex.getPackageClassesNames(String) the API returns double-package classnames like org.custom.org.custom.Foobar.
Using ClassIndex.getPackageClasses(String) seems to work. But I suppose that there is a bug writing and accessing the package jaxb.index-file fqcn-entries.
Note: Package-indexing by IndexSubclasses-annotations in package-info.java-files works fine as estimated.
The documentation recommends to subclass
org.atteo.classindex.processor.ClassIndexProcessorif you want to customize the ClassIndexProcessing. By setting custom Java-packages viaorg.atteo.classindex.processor.ClassIndexProcessor.indexPackages(String...)the processor generatesjaxb.indexfiles. Unlike the referenced jaxb-documentationthe processor generates a fqcn for all classes in the package. e.g. for package
org.customthejaxb.index-file contains class items likeorg.custom.Foobarinstead of a simple relative classnameFoobar. While accessing the classNames viaClassIndex.getPackageClassesNames(String)the API returns double-package classnames likeorg.custom.org.custom.Foobar. UsingClassIndex.getPackageClasses(String)seems to work. But I suppose that there is a bug writing and accessing the package jaxb.index-file fqcn-entries.Note: Package-indexing by IndexSubclasses-annotations in package-info.java-files works fine as estimated.