AnsweredAssumed Answered

Blaze Advisor migration from v6.1 to v7.4 issue

Question asked by ramesh.munagala@standard.com on May 11, 2017
Latest reply on May 18, 2017 by thomastravis@fico.com

Existing Blaze Advisor version is 6.1

Migrating Blaze Advisor version is 7.4

 

Import .adv file giving import failed error messages with below exceptions:

 

There were 3 exceptions while initializing the Java class provider resource.

[+] com.blazesoft.engines.rules.java.NdJavaClassImportResourceException: An exception occurred while adding the 'com.standard.apps.dice.model.factories.DICEPersistenceServicesMgr' Java class to the Java class provider resource.

Could not initialize class com.standard.apps.dice.model.factories.DICEPersistenceServicesMgr

[+] com.blazesoft.engines.rules.java.NdJavaClassImportResourceException: An exception occurred while adding the 'com.standard.apps.dice.helper.controller.DAOUtils' Java class to the Java class provider resource.

  1. java.lang.NoClassDefFoundError: com.standard.apps.dice.helper.controller.SpringUtils

[+] com.blazesoft.engines.rules.java.NdJavaClassImportResourceException: An exception occurred while adding the related classes of the 'com.standard.apps.dice.dao.CRUDDAOImpl' Java class to the Java class provider resource.

 

While importing the 'java.util.Collection filter(Object, String, Object[], org.hibernate.type.Type[])' method of the 'org.hibernate.classic.Session' class.

 

An error occurred while importing the external Java class for argument 4.

An error occurred while importing the external Java class 'Java:org.hibernate.type.Type' for a related type of the collection class '$initial_collection_name$344'.

Could not import the Java class org.hibernate.type.Type.

Cannot set the name for the mapping of the Java class 'org.hibernate.type.Type' to 'Type'.

'Type' is used already for the mapping of the Java class 'java.lang.reflect.Type'.

Outcomes