allthingssecurity commented on PR #27793: URL: https://github.com/apache/camel/pull/27793#issuecomment-6162324698
A question for part 3 of the camel-wasm work, so that it can follow this PR without waiting: the `wasm` expression language still calls a named exported function with the old alloc/dealloc + JSON-envelope protocol, while the endpoint now runs WASI command modules (since #27678). Which direction would you prefer? 1. **Move the language to the WASI model**: the expression names only a module (plus optional arguments), the message body goes to stdin, stdout is the result, a non-zero exit code fails it; predicates would need a rule (exit code 0 = true, or the printed text `true`/`false`). This changes the language options in the core model and in the Java, XML and YAML DSLs, and modules written for the old protocol stop working (upgrade note). 2. **Remove the `wasm` language** (deprecate first, or remove in 4.24 with an upgrade note), and point users to the endpoint, which does the same job as a normal route step. Option 2 is small; option 1 is a larger change across the DSLs. I am happy to do either once you have a preference. _Claude Code on behalf of allthingssecurity_ -- 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]
