eye-gu opened a new issue, #6353:
URL: https://github.com/apache/shenyu/issues/6353

   ### Is there an existing issue for this?
   
   - [x] I have searched the existing issues
   
   ### Current Behavior
   
   The WASM plugin currently depends on `wasmtime-java`, which bundles native 
libraries (`.so` / `.dylib` / `.dll`) via JNI. This causes:
   
   1. **Project inactivity** — 
[`wasmtime-java`](https://github.com/kawamuray/wasmtime-java) has not been 
actively maintained, with no recent releases or commits, making it a risk for 
bug fixes and new WASM features
   2. **Platform lock-in** — native binaries must match the deployment OS and 
arch precisely. In practice, the current test suites cannot actually load and 
execute WASM on GitHub CI because the native wasmtime library is unavailable in 
that environment. Tests are mocked with fake Java implementations that bypass 
WASM entirely, meaning **no real WASM execution is being tested**
   
   **Proposal:** Replace wasmtime-java with 
[Chicory](https://github.com/dylibso/chicory) — an actively maintained 
pure-Java WASM runtime (Apache 2.0 licensed). Benefits:
   
   - **Actively maintained** — regular releases, responsive community
   - **Runtime compilation** — Chicory's `compiler` module translates WASM 
bytecode to JVM bytecode at load time via `MachineFactoryCompiler`, 
significantly improving execution speed over interpreter mode. Also support AOT 
compilation.
   - Zero native dependencies, runs anywhere the JVM runs
   
   
   ### Expected Behavior
   
   _No response_
   
   ### Steps To Reproduce
   
   _No response_
   
   ### Environment
   
   ```markdown
   ShenYu version(s):
   ```
   
   ### Debug logs
   
   _No response_
   
   ### Anything else?
   
   I am willing to submit a 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]

Reply via email to