You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/10/16 15:23:00 UTC
[jira] [Assigned] (CAMEL-25449) camel-jbang - CLI commands use per-request action files (RuntimeHelper)
[ https://issues.apache.org/jira/browse/CAMEL-25449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-25449:
-----------------------------------
Assignee: Claus Ibsen
> camel-jbang - CLI commands use per-request action files (RuntimeHelper)
> -----------------------------------------------------------------------
>
> Key: CAMEL-25449
> URL: https://issues.apache.org/jira/browse/CAMEL-25449
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> About 30 places in the classic CLI commands (camel get, camel cmd, camel debug, ActionBaseCommand, via CamelCommand.getActionFile) still send actions through the shared <pid>-action.json / <pid>-output.json pair, so two clients asking the same integration at once can lose or swap answers.
> Since 4.21 the connector supports per-request files (<pid>-action-<requestId>.json / <pid>-output-<requestId>.json) through RuntimeHelper, which camel ask and the MCP server use. Move the CLI commands to it, keeping the shared file only as the fallback for integrations whose connector is older than 4.21.
> Part of the CLI overhaul for 4.24, together with the reliability work for agents and scripts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)