[
https://issues.apache.org/jira/browse/DERBY-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304440#comment-17304440
]
Richard N. Hillegas commented on DERBY-7108:
--------------------------------------------
Thanks for that link. I was able to look at the stack trace. It doesn't make
sense to me. I don't know anything about graalvm so I cannot contribute any
theories about how it could be failing to initialize Derby's data structures
correctly. You seem to suspect that static initialization works differently
with graalvm than with jvms which do run Derby. What is the static
initialization issue?
> Make derby graalvm friendly
> ---------------------------
>
> Key: DERBY-7108
> URL: https://issues.apache.org/jira/browse/DERBY-7108
> Project: Derby
> Issue Type: Task
> Affects Versions: 10.16.0.0
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> Hi,
> It would be neat to be able to use derby embedded with graalvm.
> Some work started at [https://github.com/apache/geronimo-arthur/tree/openjpa]
> (see [https://www.mail-archive.com/[email protected]/msg97748.html)]
> but I faced some weird issue about derby context.
> Wonder how derby community considers graalvm (h2 for example explicitly said
> it will never care about it and is happy with having broken graal support in
> a minor version which is their choice but also means there is no point
> integrating it since work can be to redo for each minor).
> If you are interested I'm happy to collaborate if needed to try to make it
> supported through arthur or native native-image configuration (can sit in the
> derby jar to work OOTB too).
> Side note: if it helps we can chat on asf slack.
> Romain
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
