Helidon
From APIDesign
| Line 5: | Line 5: | ||
Particularly tricky issue related to [[NativeImage]] is [[debugging]]. It is not easy debug [[Java]] code with [[gdb]] people tend to avoid it as much as possible. In certain situations that's however unavoidable and [[I]] tried to be as helpful as possible. I remember spending week in debugging a race condition in the database connection driver just to find out that the test is buggy and works in [[HotSpot]] mode just because [[HotSpot]] is too slow when booting up. | Particularly tricky issue related to [[NativeImage]] is [[debugging]]. It is not easy debug [[Java]] code with [[gdb]] people tend to avoid it as much as possible. In certain situations that's however unavoidable and [[I]] tried to be as helpful as possible. I remember spending week in debugging a race condition in the database connection driver just to find out that the test is buggy and works in [[HotSpot]] mode just because [[HotSpot]] is too slow when booting up. | ||
| - | [[GraalVM]] offers not only [[NativeImage]] compilation, but also polyglot capabilities. During the [[ | + | [[GraalVM]] offers not only [[NativeImage]] compilation, but also polyglot capabilities. During the [[FifthGraalAdventures]] we also modified [[Helidon]] to successfully use [[Ruby]] and [[JavaScript]] to handle incoming connections. |
Revision as of 04:54, 29 June 2020
helidon.io is a microservices framework developed four meters away from me (my seat in Oracle Prague office). As such I am the natural fit for solving complex tasks that require understanding of both sides - the JavaEE landscape as well as the GraalVM internals.
Helidon MP implements the Java Micro Profile specification based on various other standard JavaEE subspecifications including CDI. Getting Weld (the reference CDI specification) running on top of NativeImage is particularly tricky. Not only Weld dynamically scans for various annotations, but it also dynamically emits bytecode for its helper classes during runtime. Solving this required more insight into JavaEE than available among compiler engineers - not that I had it initially, but the close co-operation with Tomáš Langer (the Helidon lead engineer) helped us move forward. Tomáš prepared various trivial CDI sample projects and I was then able to get them running on NativeImage by writing a dedicated WeldFeature. Once the initial road block was gone the Helidon team was able to move forward and is now about to release Helidon 2.0. It's Micro Profile edition is going to work with NativeImage.
Particularly tricky issue related to NativeImage is debugging. It is not easy debug Java code with gdb people tend to avoid it as much as possible. In certain situations that's however unavoidable and I tried to be as helpful as possible. I remember spending week in debugging a race condition in the database connection driver just to find out that the test is buggy and works in HotSpot mode just because HotSpot is too slow when booting up.
GraalVM offers not only NativeImage compilation, but also polyglot capabilities. During the FifthGraalAdventures we also modified Helidon to successfully use Ruby and JavaScript to handle incoming connections.
Follow
