Running wasm modules in wasmer

Hi,

I’m working on integrating JVM languages with the wasmer runtime and CLI and I’m trying out TeaVM to this end. The intention is to use wasmer as a general purpose wasm execution library so that wasm modules, written in JVM languages, can be hosted in server-side processes in a language agnostic manner.

The challenge I’m facing is what to do with TeaVM’s wasm-runtime.js. Does anyone have an experience of attempting to achieve the same?

Thank you, dazraf

[dicej]

In case it’s of interest, I’ve recently been experimenting with using TeaVM to build Spin apps: https://github.com/dicej/spin-http-java. Spin is based on Wasmtime rather than Wasmer, but model is generally the same.

I expect that once the component model is fully implemented it will be pretty straightforward to host TeaVM modules in non-browser contexts by virtualizing things like teavm.logString. One could even write a general-purpose TeaVM-to-WASI virtualizer that works for any TeaVM-generated module – without needing to add specific support to TeaVM itself.

One thing that would need to change in TeaVM is to make the heap offset and data segment offset configurable so that there is room to allocate the buffers needed for canonical ABI marshalling of e.g. strings, lists, etc.

[dazraf]

@jcaesar thank you for the project link and reply. Great work. @konsoletype thank you for your guidance and your superb work with TeaVM. A fantastic achievement.

I’m a newcomer to wasm, so please forgive any misunderstandings I still have. I turned to TeaVM after my initial search and trial with GraalVM failed - their implementation is far too unstable. My work is specifically in the area of decentralised multi-network ledgers and I’m looking at wasm as a common bytecode/vm for contract definition and execution. My firm’s clients vary from startups to tier-1 financial services - hence support for a wide range of languages (including JVM languages) being a key requirement.

From my naive perspective (and with recollections of previous interface issues such as Java JNI vs Microsoft RNI) it seems to me that what may be incredibly useful for the entire wasm community is a standard ‘core’ ABI, containing common functions (each ABI has a logging facility, as an example). That way wasm modules built from disparate languages can co-exist in the wide range of application environments.

I recently found WASI which is a subgroup of the WebAssembly CG has an extensive (very large?) ABI that’s documented here. I wonder if there’s any scope in TeaVM to support WASI? Are there alternative efforts to standardise?

Thanks and regards, dazraf