wicket 1.5.4 on websphere 7

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

wicket 1.5.4 on websphere 7

Colin Chalmers
Hi all,

We have just upgraded our application running 1.4.10 to 1.5.4.
Besides the obvious compile problems all seemed to go smoothly under
jetty/tomcat but now we have a problem under websphere 7.0.11 - for clarity
the 1.4.10 version worked good under WAS7
We were running well using the filter and I've switched back to the servlet
to test if that is working but I get the same problem.

The error I am getting is this, after that the application goes into a loop
giving a 500 error

[1/31/12 1:14:27:029 EST] 0000001e webapp        W
com.ibm.ws.webcontainer.webapp.WebApp initializeStaticFileHandler
SRVE0278E: Error while adding servlet mapping --> /*.

The web.xml settings are as follows

    <servlet>
        <servlet-name>WicketServlet</servlet-name>

<servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-class>
        <init-param>
            <param-name>configuration</param-name>
            <param-value>development</param-value>
        </init-param>
        <init-param>
            <param-name>applicationBean</param-name>
            <param-value>wicketApplication</param-value>
        </init-param>
        <init-param>
            <param-name>applicationFactoryClassName</param-name>

<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>

    <servlet-mapping>
        <servlet-name>WicketServlet</servlet-name>
        <url-pattern>/*</url-pattern>
    </servlet-mapping>

I also still have *com.ibm.ws.webcontainer.invokefilterscompatibility set
to true
*
Reply | Threaded
Open this post in threaded view
|

Re: wicket 1.5.4 on websphere 7

hfriederichs
Hello,

I doubt if I can help, but in my company we also have wicket (1.5.4) on WebSphere 7 (fp21).
And it works fine, no problems. In addition to com.ibm.ws.webcontainer.invokeFiltersCompatibility we also have com.ibm.ws.webcontainer.assumefiltersuccessonsecurityerror set to true in the webcontainer. I don't recall why I did this, but it had to do with access to static files.

Hope it helps.

Regards, Hans Friederichs
Reply | Threaded
Open this post in threaded view
|

Re: wicket 1.5.4 on websphere 7

matteus

I had a problem with filter wicket and websphere and I solved the problem this way:

<servlet>
                        <servlet-name>wicket.application</servlet-name>
                        <servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-class>
                        <init-param>
                                <param-name>applicationClassName</param-name>
                                <param-value>myApplication</param-value>
                        </init-param>
                </servlet>

<servlet-mapping>
                        <servlet-name>wicket.application</servlet-name>
                        <url-pattern>/*</url-pattern>
</servlet-mapping>

Only this and its work..
See and try.