Not sure if this is related to your error, but it looks like that version of spring-security would at least require moving to spring framework 4.3.1 and possibly more dep updates as well. You should be able to run some gradle commands (dependencies, dependencyInsight, dumpDependencies) to help sort out the full list of version changes needed.
Anthony > On Aug 16, 2016, at 8:39 AM, Kevin Duling <kdul...@pivotal.io> wrote: > > I'm working on adding security to the REST methods and wanted to start by > upgrading spring-security to the latest version. > > Bumping the version from 4.1.1 from 3.1.7, I ran in to > GfshCommandsOverHttpSecurityTest failing under geode-web. The error was: > > [warn 2016/08/12 15:37:52.078 PDT <main> tid=0x1] loader constraint > violation: when resolving method "org.slf4j.impl.StaticLoggerBinder. > getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of > org/eclipse/jetty/webapp/WebAppClassLoader) of the current class, > org/slf4j/LoggerFactory, and the class loader (instance of > sun/misc/Launcher$AppClassLoader) for the method's defining class, > org/slf4j/impl/StaticLoggerBinder, have different Class objects for the > type org/slf4j/ILoggerFactory used in the signature > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" > the class loader (instance of org/eclipse/jetty/webapp/WebAppClassLoader) > of the current class, org/slf4j/LoggerFactory, and the class loader > (instance of sun/misc/Launcher$AppClassLoader) for the method's defining > class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for > the type org/slf4j/ILoggerFactory used in the signature
signature.asc
Description: Message signed with OpenPGP using GPGMail
