ammachado opened a new pull request, #24157: URL: https://github.com/apache/camel/pull/24157
# Description Continues [CAMEL-23535](https://issues.apache.org/jira/browse/CAMEL-23535). This PR covers batches 21-25: **28 files** in `core/camel-api` received enhanced class-level Javadoc. The changes are documentation-only; no method signatures, annotations, or production code were altered. **Batch 21 — Bean post-processing and DI SPIs** (`spi/`) `CamelBeanPostProcessor`, `CamelBeanPostProcessorInjector`, `CamelDependencyInjectionAnnotationFactory`, `Injector`, `DependencyStrategy` **Batch 22 — CamelContext lifecycle event SPIs** (`spi/`) `OnCamelContextEvent` and its six phase sub-interfaces: `OnCamelContextInitializing`, `OnCamelContextInitialized`, `OnCamelContextStarting`, `OnCamelContextStarted`, `OnCamelContextStopping`, `OnCamelContextStopped` **Batch 23 — Property configurer SPIs** (`spi/`) `PropertyConfigurer`, `PropertyConfigurerAware`, `PropertyConfigurerGetter`, `ExtendedPropertyConfigurerGetter`, `GeneratedPropertyConfigurer` **Batch 24 — Properties source SPIs** (`spi/`) `PropertiesSource`, `PropertiesSourceFactory`, `LoadablePropertiesSource`, `PropertiesResolvedValue`, `PropertiesReload` **Batch 25 — Resource loading SPIs** (`spi/`) `Resource`, `ResourceAware`, `ResourceLoader`, `ResourceResolver`, `ResourceReload`, `ResourceReloadStrategy` Each file received: - A clear opening sentence naming its role in the Camel system - An architecture paragraph with `{@link}` references and explanation of callers/lifecycle - A user-manual `<a href>` link where a matching page exists (`property-binding`, `using-propertyplaceholder`, `route-reload`, `bean-injection`, `bean-integration`, `lifecycle`) - `@see` tags for closely related sibling types - Preserved `@since` tags While reworking `OnCamelContextEvent`, two dangling `@see` references to the non-existent `OnCamelContextStart` and `OnCamelContextStop` types were removed. The four core resource types (`Resource`, `ResourceAware`, `ResourceLoader`, `ResourceResolver`) intentionally omit an `<a href>` because no matching user-manual page exists. Verification performed for each batch: style matched against previously enhanced files, `mvn formatter:format impsort:sort` touched only the intended files, and `mvn compile` on `core/camel-api` passed. Class-level Javadoc does not affect generated catalog files, so no generated changes were produced. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL-23535) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn formatter:format impsort:sort` and `mvn compile` on `core/camel-api` locally and committed all changes. (Documentation-only change; no auto-generated files are affected.) _Claude Code on behalf of Adriano Machado_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
