ammachado opened a new pull request, #23311:
URL: https://github.com/apache/camel/pull/23311

   # Description
   
   [CAMEL-23535](https://issues.apache.org/jira/browse/CAMEL-23535) asks for an 
audit and enhancement of the javadoc in `core/camel-api` so that classes better 
explain what they are, what they do, and how they fit into the framework, with 
links to the relevant user-manual pages.
   
   This PR is the **first batch** of that work: class-level javadoc on the 
**lifecycle and context** family of top-level public-API types. Scope is 
intentionally narrow so the prose style can be reviewed before the rest of 
`core/camel-api` is updated.
   
   ## Changes
   
   Class-level javadoc expanded on 18 top-level types in `org.apache.camel`:
   
   - **Context:** `CamelContext`, `CamelContextAware`, `CamelContextLifecycle`, 
`CatalogCamelContext`, `ExtendedCamelContext`, `ContextEvents`
   - **Service lifecycle:** `Service`, `ServiceStatus`, `StatefulService`
   - **Exceptions:** `RuntimeCamelException`, `CamelException`, 
`CamelExchangeException`, `AlreadyStoppedException`, 
`FailedToCreateRouteException`, `FailedToStartRouteException`, 
`FailedToStartComponentException`, `FailedToCreateConsumerException`, 
`FailedToCreateProducerException`
   
   Each updated docblock follows the same pattern: a one-sentence what-it-is, a 
paragraph on the role in routing / lifecycle, sibling-type `{@link}` 
references, and (where a matching user-manual page exists) one `<a 
href="https://camel.apache.org/manual/...";>` link. The convention matches the 
existing javadoc style in `Endpoint.java`, `Component.java`, `Processor.java`, 
`Message.java`, `Route.java`.
   
   The change is **comment-only**: no signatures, behaviour, or runtime code is 
altered.
   
   ## Out of scope (follow-ups)
   
   - Public-method javadoc gap-filling in `core/camel-api`.
   - The rest of the top-level `org.apache.camel.*` surface (messaging core, 
endpoints/components/producers/consumers, routes & builders, annotations & 
functional types) will land as subsequent batches under the same JIRA.
   - `org.apache.camel.spi.*` and other sub-packages (catalog, console, 
cloudevents, cluster, clock, ai, health, vault, resume, trait, support).
   
   # 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.
   
   # 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 clean install -DskipTests\` locally from root folder 
and I have committed all auto-generated changes.
   
   ---
   
   _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]

Reply via email to