Mike Beckerle created DAFFODIL-2591:
---------------------------------------
Summary: Negative TDML Test causes reflective access serialization
error using Java 17
Key: DAFFODIL-2591
URL: https://issues.apache.org/jira/browse/DAFFODIL-2591
Project: Daffodil
Issue Type: Bug
Components: General
Affects Versions: 3.1.0
Reporter: Mike Beckerle
I have a reproducible case where I build daffodil from source using Java 17, I
publishLocal, then I have a DFDL schema project where one test fails - a
TDML-based negative test.
The error has to do with reflective access and object deserialization - there
are reflective capabilities that are no longer supported in Java 17; however,
the question is why does this one negative TDML test cause this error when
many/most other things do not.
Unfortunately, the DFDL schema for this is non-public. It is called the p8
schema for reference purposes.
I've listed this as minor priority because using Java 11, or Java 8 for the
DFDL schema, this problem does not occur, even if Daffodil itself was built
with a Java 17 JVM.
Note that this test was done AFTER the daffodil git commit
bf576e8be961016df11b2b3caf50e0d8f9616867 which adds the "-release 8" to scalac
and javac options.
Is it the case that one must use these -release 8 options for a DFDL schema
project (which contains scala test driver code) as well in order to avoid this
compatibility error?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
