Skip to content

Conversation

chirino
Copy link
Contributor

@chirino chirino commented May 15, 2025

No description provided.

chirino added 2 commits May 15, 2025 08:58
Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
@chirino chirino requested a review from a team as a code owner May 15, 2025 13:01
Copy link

@andreaTP andreaTP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, better than current 👍


### Compiling WASM to Bytecode (Experimental)

By default, wsm modules are executed using the [Chicory](https://chicory.dev/) interpreter. But if you want the wasm to

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
By default, wsm modules are executed using the [Chicory](https://chicory.dev/) interpreter. But if you want the wasm to
By default, wasm modules are executed using the [Chicory](https://chicory.dev/) interpreter. But if you want the wasm to

Chicory supports compiling the WASM module at either build time or runtime. If you want to compile your Quarkus app to
native, then you MUST compile the WASM module at build (time to avoid the use of runtime reflection). Please refer
to the [Chicory documentation](https://chicory.dev/docs/) for more details on how to compile the WASM module to Java
bytecode. Compiling will produce a machine factory that you should pass as an argument to the [withMachineFactory](https://javadoc.io/doc/io.roastedroot/proxy-wasm-java-host/latest/io/roastedroot/proxywasm/Plugin.Builder.html#withMachineFactory(java.util.function.Function))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An example on how to achieve it(e.g. maven plugin setup etc. etc.) would be great.

@chirino chirino merged commit 780b3a8 into quarkiverse:main May 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants