[
https://issues.apache.org/jira/browse/DERBY-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305027#comment-17305027
]
Bryan Pendleton commented on DERBY-7108:
----------------------------------------
Derby's code generation behavior has been a problem for other variant Java
implementations in the past.
For example, DERBY-4458 was a hard blocker for use of Derby with the "Dalvik"
variant of Java.
As far as I know, if this is the problem with "graalvm", then it may be a
pretty big challenge, as Derby is quite dependent on being able to dynamically
generate and subsequently execute bytecode.
> 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
> Attachments: outs.zip
>
>
> 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)
