On Thu, Apr 25, 2019 at 3:07 PM Rémy Maucherat <r...@apache.org> wrote:
> On Wed, Apr 24, 2019 at 6:29 PM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> Awesome news Rémy, thanks for sharing! >> > > Next roadblock is https://github.com/oracle/graal/issues/684 > It's probably not 100% mandatory but I'd rather have a minimum of > flexibility (I'm not a big believer of Java only embedding since > configuration can get complex fast and it's harder to maintain long term). > > Feel free to help if you'd like. > Ok, so after configuring reflection to some extent in order to examine the behavior, I am now rather confident things might work out eventually. I thought the best strategy was to add tracing to Tomcat and have the user do a regular run with its config to generate the reflection json. In the end, I found that there's a tool to do that already in graal, in the form of a jvm agent. I then ran into https://github.com/oracle/graal/issues/1194 (exact same crash trace), not sure about any workaround so I'll wait for the issue to be resolved in a future RC. Rémy
