Fix spring transaction issue in getNodetemplates 33/127933/2
authorrameshiyer27 <ramesh.murugan.iyer@est.tech>
Mon, 21 Mar 2022 00:00:03 +0000 (00:00 +0000)
committerrameshiyer27 <ramesh.murugan.iyer@est.tech>
Tue, 22 Mar 2022 13:16:48 +0000 (13:16 +0000)
changes on the db service template object gets auto updated to the db
by spring transaction. Creating new object copy to avoid the same.

Issue-ID: POLICY-3934
Signed-off-by: zrrmmua <ramesh.murugan.iyer@est.tech>
Change-Id: I0dbd5cb9d2c1119b2f263f60ed470bc8fef85d1e

main/src/main/java/org/onap/policy/api/main/service/ToscaServiceTemplateService.java

index d578d0d..2e8fc9e 100644 (file)
@@ -550,14 +550,13 @@ public class ToscaServiceTemplateService {
         throws PfModelException {
         LOGGER.debug("->getNodeTemplate: name={}, version={}", name, version);
         List<ToscaNodeTemplate> nodeTemplates = new ArrayList<>();
-        var jpaNodeTemplates = new JpaToscaNodeTemplates();
 
         var dbServiceTemplate = getDefaultJpaToscaServiceTemplate();
         //Return empty if no nodeTemplates present in db
         if (!ToscaUtils.doNodeTemplatesExist(dbServiceTemplate)) {
             return nodeTemplates;
         }
-        jpaNodeTemplates = dbServiceTemplate.getTopologyTemplate().getNodeTemplates();
+        var jpaNodeTemplates = new JpaToscaNodeTemplates(dbServiceTemplate.getTopologyTemplate().getNodeTemplates());
 
         //Filter specific nodeTemplates
         if (name != null && version != null) {