RE: Migration from servlet to filter always serves WebApplication.getHomePage() when I click on links
Hi, I struggled with similar problems with OC4J. Unorthodoxid solution we found was: Add index.html into context root - no matter what is the content of it. However, you cannot use this solution with Weblogic (10). Br Harri Ps. Check this also: http://www.nabble.com/Wicket-cannot-work-on-OC4J-%28ias-10g%29--td16738242.html#a16738242 -Original Message- From: ext mallet [mailto:ryanlahue...@gmail.com] Sent: 03 March, 2009 01:20 To: users@wicket.apache.org Subject: Re: Migration from servlet to filter always serves WebApplication.getHomePage() when I click on links Thanks for the quick response Igor. I'm running OC4J... I changed the mapping as you suggested but am now getting a 403/Directory browsing not allowed. Once I find a way to coerce oc4j into allowing directory browsing I will post an update -- having some trouble getting my orion-web.xml changes to take, but this is not a wicket issue. igor.vaynberg wrote: try with /* mapping and see if it works you are not running this on websphere are you? -igor On Mon, Mar 2, 2009 at 2:12 PM, mallet ryanlahue...@gmail.com wrote: Hello, I am using 1.3 and a servlet for Wicket in my web.xml, which I've pasted below. I am trying to change to using a Filter instead, which I also pasted below, but I get a weird behavior -- my WebApp.getHomePage() is served every time I click on a link. The links work fine when I use the servlet, and I followed the migration guide ( http://cwiki.apache.org/WICKET/migrate-13.html#Migrate-1.3-Filterinst eadofaServlet ), so I am not sure why I am getting this behavior. Any ideas? --- !-- This works -- servlet servlet-nameMyWebApp/servlet-name servlet-classorg.apache.wicket.protocol.http.WicketServlet/servlet -class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameMyWebApp/servlet-name url-pattern/app/*/url-pattern /servlet-mapping --- !-- This does not work -- filter filter-nameMyWebApp/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-cl ass init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param /filter filter-mapping filter-nameMyWebApp/filter-name url-pattern/app/*/url-pattern /filter-mapping -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-serves- WebApplication.getHomePage%28%29-when-I-click-on-links-tp22298026p222 98026.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-s erves-WebApplication.getHomePage%28%29-when-I-click-on-links-tp 22298026p22299235.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Migration from servlet to filter always serves WebApplication.getHomePage() when I click on links
Hello, I am using 1.3 and a servlet for Wicket in my web.xml, which I've pasted below. I am trying to change to using a Filter instead, which I also pasted below, but I get a weird behavior -- my WebApp.getHomePage() is served every time I click on a link. The links work fine when I use the servlet, and I followed the migration guide ( http://cwiki.apache.org/WICKET/migrate-13.html#Migrate-1.3-FilterinsteadofaServlet ), so I am not sure why I am getting this behavior. Any ideas? --- !-- This works -- servlet servlet-nameMyWebApp/servlet-name servlet-classorg.apache.wicket.protocol.http.WicketServlet/servlet-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameMyWebApp/servlet-name url-pattern/app/*/url-pattern /servlet-mapping --- !-- This does not work -- filter filter-nameMyWebApp/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param /filter filter-mapping filter-nameMyWebApp/filter-name url-pattern/app/*/url-pattern /filter-mapping -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-serves-WebApplication.getHomePage%28%29-when-I-click-on-links-tp22298026p22298026.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migration from servlet to filter always serves WebApplication.getHomePage() when I click on links
try with /* mapping and see if it works you are not running this on websphere are you? -igor On Mon, Mar 2, 2009 at 2:12 PM, mallet ryanlahue...@gmail.com wrote: Hello, I am using 1.3 and a servlet for Wicket in my web.xml, which I've pasted below. I am trying to change to using a Filter instead, which I also pasted below, but I get a weird behavior -- my WebApp.getHomePage() is served every time I click on a link. The links work fine when I use the servlet, and I followed the migration guide ( http://cwiki.apache.org/WICKET/migrate-13.html#Migrate-1.3-FilterinsteadofaServlet ), so I am not sure why I am getting this behavior. Any ideas? --- !-- This works -- servlet servlet-nameMyWebApp/servlet-name servlet-classorg.apache.wicket.protocol.http.WicketServlet/servlet-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameMyWebApp/servlet-name url-pattern/app/*/url-pattern /servlet-mapping --- !-- This does not work -- filter filter-nameMyWebApp/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param /filter filter-mapping filter-nameMyWebApp/filter-name url-pattern/app/*/url-pattern /filter-mapping -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-serves-WebApplication.getHomePage%28%29-when-I-click-on-links-tp22298026p22298026.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migration from servlet to filter always serves WebApplication.getHomePage() when I click on links
Thanks for the quick response Igor. I'm running OC4J... I changed the mapping as you suggested but am now getting a 403/Directory browsing not allowed. Once I find a way to coerce oc4j into allowing directory browsing I will post an update -- having some trouble getting my orion-web.xml changes to take, but this is not a wicket issue. igor.vaynberg wrote: try with /* mapping and see if it works you are not running this on websphere are you? -igor On Mon, Mar 2, 2009 at 2:12 PM, mallet ryanlahue...@gmail.com wrote: Hello, I am using 1.3 and a servlet for Wicket in my web.xml, which I've pasted below. I am trying to change to using a Filter instead, which I also pasted below, but I get a weird behavior -- my WebApp.getHomePage() is served every time I click on a link. The links work fine when I use the servlet, and I followed the migration guide ( http://cwiki.apache.org/WICKET/migrate-13.html#Migrate-1.3-FilterinsteadofaServlet ), so I am not sure why I am getting this behavior. Any ideas? --- !-- This works -- servlet servlet-nameMyWebApp/servlet-name servlet-classorg.apache.wicket.protocol.http.WicketServlet/servlet-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameMyWebApp/servlet-name url-pattern/app/*/url-pattern /servlet-mapping --- !-- This does not work -- filter filter-nameMyWebApp/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuemy.WebApp/param-value /init-param /filter filter-mapping filter-nameMyWebApp/filter-name url-pattern/app/*/url-pattern /filter-mapping -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-serves-WebApplication.getHomePage%28%29-when-I-click-on-links-tp22298026p22298026.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Migration-from-servlet-to-filter-always-serves-WebApplication.getHomePage%28%29-when-I-click-on-links-tp22298026p22299235.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
