Werner Punz created MYFACES-4473:
------------------------------------

             Summary: Integration Tests dependency issue
                 Key: MYFACES-4473
                 URL: https://issues.apache.org/jira/browse/MYFACES-4473
             Project: MyFaces Core
          Issue Type: Bug
    Affects Versions: 4.0.0-RC1
         Environment: Java 11
            Reporter: Werner Punz


The integration tests atm, have a problem with a servlet implementation coming 
in, not reflecting the actual layer.

SCHWERWIEGEND: Servlet.service() for servlet [FacesServlet] in context with 
path [/ajax-4.0.0-SNAPSHOT] threw exception ['java.lang.String 
jakarta.servlet.SessionCookieConfig.getAttribute(java.lang.String)'] with root 
cause
java.lang.NoSuchMethodError: 'java.lang.String 
jakarta.servlet.SessionCookieConfig.getAttribute(java.lang.String)'
    at 
org.apache.myfaces.context.flash.FlashImpl._createFlashCookie(FlashImpl.java:1194)
    at 
org.apache.myfaces.context.flash.FlashImpl._saveRenderFlashMapTokenForNextRequest(FlashImpl.java:774)
    at 
org.apache.myfaces.context.flash.FlashImpl._manageFlashMapTokens(FlashImpl.java:889)
    at 
org.apache.myfaces.context.flash.FlashImpl.doPrePhaseActions(FlashImpl.java:197)
    at 
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:155)
    at 
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:125)
    at jakarta.faces.webapp.FacesServlet.service(FacesServlet.java:223)

 

The called api is present, but somewhere still an old servlet impl is pushed 
into the container.

I have tried to upgrade to tomcat embedded 10, no dice. The api is correctly 
referenced though and I can see it from the ide.

My idea is that Aquilian might push an old servlet definition in during runtime.

Also the currently used Aquilian is incompatible with the latest jdks. (Proxy 
mechanism, which is used causes errors on the latest jdk)

I am still searching where the issue stems from, but so far no luck on my side.

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to