Spring Security
  1. Spring Security
  2. SEC-1292

Update springframework.web to servlet 3.0

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: 3.0.0.RC2
    • Component/s: Web
    • Labels:
      None

      Description

      My WebApp don`t want to start with glassfish and Springframework 3.0RC1
      Seems spting need to be updated to servlet 3.0

      SEVERE: Exception while loading the app
      java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.VerifyError: (class: org/springframework/security/web/authentication/AbstractAuthenticationProcessingFilter, method: successfulAuthentication signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;Lorg/springframework/security/core/Authentication;)V) Incompatible argument to function
      at com.sun.enterprise.web.WebApplication.start(WebApplication.java:118)
      at org.glassfish.internal.data.EngineRef.start(EngineRef.java:126)
      at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:231)
      at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:231)
      at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:323)
      at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:169)
      at org.glassfish.web.osgi.JavaEEDeploymentRequest.deploy(JavaEEDeploymentRequest.java:167)
      at org.glassfish.web.osgi.JavaEEDeploymentRequest.execute(JavaEEDeploymentRequest.java:119)
      at org.glassfish.web.osgi.OSGiWebContainer.deployJavaEEArtifacts(OSGiWebContainer.java:147)
      at org.glassfish.web.osgi.OSGiWebContainer.deploy(OSGiWebContainer.java:111)
      at org.glassfish.web.osgi.WebExtender.deploy(WebExtender.java:166)
      at org.glassfish.web.osgi.WebExtender.bundleChanged(WebExtender.java:118)
      at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:919)
      at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
      at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
      at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1350)
      at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1301)
      at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:338)
      at org.eclipse.osgi.framework.internal.core.AbstractBundle.updateWorker(AbstractBundle.java:625)
      at org.eclipse.osgi.framework.internal.core.AbstractBundle.update(AbstractBundle.java:572)
      at org.apache.felix.fileinstall.DirectoryWatcher.update(DirectoryWatcher.java:786)
      at org.apache.felix.fileinstall.DirectoryWatcher.update(DirectoryWatcher.java:679)
      at org.apache.felix.fileinstall.DirectoryWatcher.doInstalled(DirectoryWatcher.java:380)
      at org.apache.felix.fileinstall.DirectoryWatcher.run(DirectoryWatcher.java:123)
      Nov 2, 2009 2:47:10 PM JavaEEDeploymentRequest deploy

        Activity

        Hide
        Luke Taylor added a comment -

        Glassfish 3 is in a preview release version and I believe that is the only version that contains a servlet 3.0 implementation. I don't really understand why there should be a problem here. This is just a method which takes a standard HttpServletRequest and HttpServletResponse and to the best of my knowledge these should be backwards compatible in servlet 3.0.

        Given its current state, this seems likely to be a Glassfish problem. If you disagree, please expand on what you think needs to be updated?

        Also, with a something like a Java VerifyError, it would be helpful if you include the versions you are using (of Java and glassfish).

        Show
        Luke Taylor added a comment - Glassfish 3 is in a preview release version and I believe that is the only version that contains a servlet 3.0 implementation. I don't really understand why there should be a problem here. This is just a method which takes a standard HttpServletRequest and HttpServletResponse and to the best of my knowledge these should be backwards compatible in servlet 3.0. Given its current state, this seems likely to be a Glassfish problem. If you disagree, please expand on what you think needs to be updated? Also, with a something like a Java VerifyError, it would be helpful if you include the versions you are using (of Java and glassfish).
        Hide
        Luke Taylor added a comment -

        No further information Closing.

        Show
        Luke Taylor added a comment - No further information Closing.

          People

          • Assignee:
            Luke Taylor
            Reporter:
            Pavel Kuzin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: