Adriano Machado created CAMEL-23864:
---------------------------------------
Summary: edi-x12-as2 and openapi/server JBang examples fail after
YAML normalization
Key: CAMEL-23864
URL: https://issues.apache.org/jira/browse/CAMEL-23864
Project: Camel
Issue Type: Bug
Components: camel-jbang
Reporter: Adriano Machado
Two examples in camel\-jbang\-examples fail their Citrus integration tests
\(verified locally with Camel 4.18.2 / Citrus 4.10.1\). Both regressions were
introduced by the YAML canonical\-form normalization in commit 60a70d8.
h3. edi\-x12\-as2/camel/edi\-x12\-as2.camel.yaml
\* onException was moved out of the {{as2Error}} routeConfiguration into the
route steps, producing "Route receivePurchaseOrder has no output processors" at
startup. Fix: restore onException \(with the AS2 disposition\-FAILED script
handler\) into the routeConfiguration, matching the canonical YAML form.
\* {{ediMessageCharset: charset=US\-ASCII}} is an invalid charset name and
triggers IllegalCharsetNameException. Fix: use {{US\-ASCII}}. Latent since the
example was added; only surfaced once the route started correctly.
h3. openapi/server/petstore.camel.yaml
\* The restConfiguration block containing {{apiContextPath: openapi}} was
deleted, so the OpenAPI spec was no longer served at /openapi and the test
received HTTP 404 \(Resource not found\). Fix: restore the restConfiguration
with {{clientRequestValidation: true}} and {{apiContextPath: openapi}}.
h3. ftp example \(maintenance\)
\* Move the runtime dependency declarations from jbang.properties
\({{run.deps}}\) to {{camel.jbang.dependencies}} in application.properties,
which Camel JBang supports natively as a comma\-separated list.
After these fixes all 8 workflow test suites pass.
Related to CAMEL\-23863 \(another regression from the same YAML normalization
pass\).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
