-
Bug
-
Resolution: Done
-
Major
-
7.13.2.GA
-
False
-
False
-
-
-
-
-
-
CR1
-
?
-
2023 Week 06-08 (from Feb 6)
Could not parse mapping document: file: jbpm-kie-services-7.67.0.Final-redhat-00017.jar!/META-INF/Servicesorm.xml
Findings:
- Servicesorm.xml in jbpm-kie-services-77.67.0.Final-redhat-00017.jar has entity-mappings with orm_2_0.xsd, which does not defines “constructor-result” which is available at line number 1006.
- The named-query and named-native-query tags appear after tag “sql-result-set-mapping”. I believe ordering is necessary for the xml to be parsed.
Resolution:
Modify Servicesorm.xml for below changes.
- Change entity-mappings to reflect orm 2.1 by performing below change, this is need so as to have “constructor-result” as it is defined with orm_2_1.xsd.
<entity-mappings xmlns=http://xmlns.jcp.org/xml/ns/persistence/orm xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=http://xmlns.jcp.org/xml/ns/persistence/orm orm_2_1.xsd version="2.1">
- Order the named-query and named-native-query tags in the sequence as per xsd definition (mention under xsd:sequence).
To correct, cut lines from 1029 through 1504 and place it at line 1004 (before tag sql-result-set-mapping).
- clones
-
JBPM-9946 jbpm-kie-services, Servicesorm.xml incorrect version of orm used
- Resolved