SmartClient does not depend on Spring unless you specifically use Spring-specific features, such as serverObject or dataSource.serverConstructor supporting a Spring reference.
So you can use whatever Spring version you like unless you specifically use those convenience features, and its straightforward to achieve the same result without using those features.
As far as the problem you might be having:
1. Which specific SmartClient-Spring integration points are you trying to use?
2. Which ones of those are creating an issue for you, and what specific is the issue?
The ideal information here is a SmartClient server log with a stack trace showing what failed if something failed, and all files necessary to reproduce the issue.
Thank you for getting back quickly.
We're not actually having an issue currently - we just have dependency flagged as out of support.
We use serverObject for almost all data sources.
Do you think we should be able to upgrade to spring 6.2.x jars for SmartGWT 13.1 ?
Unfortunately, Spring keeps breaking backwards compatibility with new releases, creating major headaches for framework providers like us.
You can generally update to new minor versions of Spring .jars, but not major.
If you need to update Spring without updating SmartGWT, the simplest thing is to just not use the Spring-specific serverObject support, and just use the generic support (by classname, etc), which will work with any version of Spring.
Comment