Describe the bug
I am working on a project that is still on eclipselink 2.6.2. When updating to anything higher, I observe an issue with unmarshalling xml's that contain a namespace, i.e:
There is no explicit exception as such, but the resulting DynamicEntity will have the object keys, but without value (such that entity.get("modelId") returns null.
To Reproduce
Steps/resources to reproduce the behavior:
EclipseLink version: 2.6.3
Java/JDK version: Java 8
Entity source (mainly applied annotations)
For problem in MOXy (JAXB implementation)
Describe the bug I am working on a project that is still on eclipselink
2.6.2
. When updating to anything higher, I observe an issue with unmarshalling xml's that contain a namespace, i.e:There is no explicit exception as such, but the resulting
DynamicEntity
will have the object keys, but without value (such thatentity.get("modelId")
returnsnull
.To Reproduce Steps/resources to reproduce the behavior:
DynamicJAXBContext
is created for each schema version (v10-v29)NodeIngestor
holds that context. It is retrieved withnodeIngestor.getContextForVersion(new SchemaVersion("v14"))
(see test case)I have created the following change request to reproduce the behaviour: Add test case that tests jaxb unmarshalling of xml It contains the following test:
To check it out and run it:
git fetch https://gerrit.onap.org/r/aai/aai-common refs/changes/46/138646/2 && git checkout -b change-138646 FETCH_HEAD
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
)cd aai-core && mvn test -Dcheckstyle.skip -Dtest=MoxyEngineTest#moxyTest
eclipse.persistence.version
in the pom.xml to2.6.3
and rerun the testmvn test [...] -Dmaven.surefire.debug
can be used to enable remote debuggingExpected behavior That unmarshalling works for both versions, such that
dynamicEntity.get("myAttribute")
returns a value != null.