[
https://issues.apache.org/jira/browse/DERBY-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304400#comment-17304400
]
Romain Manni-Bucau commented on DERBY-7108:
-------------------------------------------
Hi Rick
Hope this one will work (otherwise maybe grab today's geronimo dev list
archives):
[https://www.mail-archive.com/dev@geronimo.apache.org/msg97748.html]
Long story short the language context is null in current version when executing
first statement.
I dont know if the easiest is to grab a debug version and trace things or
something else so knowledge of missing reflection metadata, resource or runtime
static blocks init (graal captures it at build time then runtime inherits from
it) can ease to solve the current issue. My suspicion is the static
registration vs runtime but didnt get time to dig more.
Goal of this ticket is to see how I/we move forward on the medium/long term.
What I really dont want is to make it work then derby break it in next version
unintentionally so some derby dev knowledge sharing about arthur or graal is
also a goal of this ticket and effort sharing.
Not sure how yet so any proposal is welcomed :). I think that trying to run
this openjpa sample can be a good start but alternatives like a more atomic
sample would work too.
Hope it makes sense.
> 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/dev@geronimo.apache.org/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)
