Skip to content

Audit and update deprecated Camel component usage for 4.21.0 #2830

Description

@oscerd

Description

With the move to Camel 4.21.0, the kamelet catalog should be audited for any Camel components or options that have been deprecated in Camel 4.20+ and updated to use their recommended replacements.

The catalog currently uses 109 unique Camel components across 252 kamelets. Some of these components or their configuration options may have been deprecated in recent Camel releases.

Expected Behavior

  • All 252 kamelets use only non-deprecated Camel components and configuration options
  • Any deprecated usages are replaced with their recommended alternatives
  • The catalog is fully compatible with Camel 4.21.0 without deprecation warnings

Steps

  1. Cross-reference the Camel 4.20 and 4.21 release notes and migration guides for deprecated components
  2. Grep the kamelets/ directory for any usage of deprecated components or options
  3. Update affected kamelets to use the recommended replacements
  4. Validate all updated kamelets pass the script/validator

Additional Context

  • The most heavily used components are: camel:jackson (90 kamelets), camel:kafka (23), camel:sql (16), camel:jsonpath (13), camel:http (11), camel:jms (10)
  • Target release: 4.21.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions