Error regarding missing isomorphic_spring.jar file after upgrading to 5.1d

[stonebranch3]

Hi Isomorphic,

I recently upgraded to SNAPSHOT_v10.1d_2015-07-16/Pro Deployment (built 2015-07-16) and started seeing the following error message:

Unable to instantiate class 'com.isomorphic.spring.SpringBeanFactory' - check to make sure you have isomorphic_spring.jar (and its dependencies: isomorphic_core_rpc.jar, spring-core-3.2.10.RELEASE.jar, groovy-2.3.6.jar, commons-jxpath-1.3.jar, commons-pool-1.6.jar, spring-aop-3.2.10.RELEASE.jar, httpcore-4.3.2.jar, xml-apis-1.3.04.jar, commons-logging-1.1.1.jar, xercesImpl-2.9.1.jar, commons-fileupload-1.3.1.jar, aopalliance.jar, commons-lang-2.6.jar, commons-vfs-1.0.jar, poi-ooxml-schemas-3.9-20121203.jar, activation.jar, poi-ooxml-3.9-20121203.jar, isc-jakarta-oro-2.0.6.jar, groovy-sql-2.3.6.jar, log4j-1.2.17.jar, slf4j-api-1.7.7.jar, spring-tx-3.2.10.RELEASE.jar, joda-time-2.3.jar, spring-beans-3.2.10.RELEASE.jar, xmlbeans-2.3.0.jar, spring-jdbc-3.2.10.RELEASE.jar, commons-io-2.2.jar, velocity-1.7.jar, spring-webmvc-3.2.10.RELEASE.jar, spring-context-3.2.10.RELEASE.jar, spring-orm-3.2.10.RELEASE.jar, commons-cli-1.2.jar, hibernate-validator-4.1.0.Final.jar, mail.jar, javax.persistence.jar, groovy-jsr223-2.3.6.jar, poi-3.9-20121203.jar, spring-web-3.2.10.RELEASE.jar, validation-api-1.0.0.GA.jar, commons-collections-3.2.1.jar, spring-expression-3.2.10.RELEASE.jar, httpclient-4.3.5.jar, commons-codec-1.6.jar) in your CLASSPATH

We are using lookupStyle="new" not lookupStyle="spring" for our DMIs and would prefer not to include unused jars.

I found the following forum post for a similar issue. It looks like this was fixed at one point.

http://forums.smartclient.com/showthread.php?t=32622&highlight=isomorphic_spring.jar

Thanks.

[Isomorphic]

We did find a few additional instances of spring lookup attempts in the RPC codepath that will be fixed in the next nightly build (Jul 23 2015).

Thanks for reporting this - and please let us know if you continue to encounter these.

[stonebranch3]

I'm no longer seeing these messages with the July 23 build.

Thanks.