[ 
https://issues.apache.org/jira/browse/CAMEL-26591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-26591.
---------------------------------
    Resolution: Fixed

> camel-jbang - AI tools: an & in an endpoint parameter, the headers a cut 
> answer leaves out, find with several words, and the closest option of an EIP
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26591
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26591
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang, camel-jbang-mcp
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> Follow-ups from the r26 run of the local-model benchmark and the reviews of 
> CAMEL-26568 and CAMEL-26572:
> * An & in a value under the parameters: of an endpoint, such as filterFile: 
> "${file:name} contains 'R&D'". The YAML DSL adds the parameters to the uri as 
> they are (YamlSupport.createEndpointUri does not encode them), so Camel reads 
> filterFile=${file:name} contains 'R and takes the rest as another option: the 
> route fails, or a lenient component takes a cut value. The check refused it, 
> but with "Unknown option 'D''", which does not say why. It now gives one 
> message that says to write the value in RAW(...). A secret option, which the 
> YAML DSL puts in RAW itself, is no longer refused.
> * camel_catalog_doc with includeHeaders=true is cut by the size limit: for 
> aws2-s3 it shows 3 of 54 headers, and CamelAwsS3Key is not among them. The 
> answer now names the headers it left out, so that the model can ask for one.
> * camel_catalog_find does not split words: "aws2-s3 header KEY" finds 
> nothing, while the words one by one would.
> * A filter with no match on an EIP gets no closest options; only components 
> have them. restConfiguration with optionsFilter=componentName pointed to 
> rest-openapi and rest-postman, while restConfiguration's own option component 
> is what the model wanted.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to