ramu11 commented on PR #25778: URL: https://github.com/apache/camel/pull/25778#issuecomment-5438115879
> Agree @ramu11 , in particular > > ``` > Controlled Exchange mutation helpers. > A controlled Camel/Java host API. > ``` > > I think we can come up with a facade that limits the context/exchange functionalities Agreed. I looked into this direction, and a small, controlled façade appears technically feasible without exposing the full Exchange or Java object graph. A namespaced API such as camel.getHeader(...), camel.setHeader(...), camel.getProperty(...), and camel.setBody(...) would fit the QuickJS4J host-function model well. Values can remain JSON-based, so we avoid live Java references and general Java interop. There are a few lifecycle details to handle because QuickJS engines are reused, particularly ensuring host callbacks are associated only with the current Exchange. I think this would be best explored as a separate follow-up JIRA after the initial Preview implementation is merged, rather than expanding this PR. -- 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]
