RE: Any solution for the context problem with the relative links of BookmarkablePageLink?
Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? -- Jeremy Thomerson http://www.wickettraining.com On Sat, May 8, 2010 at 12:40 AM, Chris Colman chr...@stepaheadsoftware.comwrote: I'll explain the problem in detail. I think it's similar to the link I provided but maybe not: I have a site whose home page that is rendered via: www.mysite.com/content/home/pName/pValue but obviously the users will get their via: www.mysite.com I want the home page to be serviced via a forward to www.mysite.com/content/home/pName/pValue so that the search engines don't have to experience a 301 redirect. (where pName/pValue are required parameters that can be passed to any page) I forward via: RequestDispatcher rd = servletContext. getRequestDispatcher(www.mysite.com/content/home/pName/pValue); rd.forward(req, res); I don't mind if all subsequent pages a user visits use the full form of the URL and these full URLs appear in the browser address bar. Eg., www.mysite.com/content/contactUs/pName/pValue www.mysite.com/content/products/pName/pValue www.mysite.com/content/home/pName/pValue The forward works fine but any links on that page don't work because the context of the wicket web app is 'content' - a separate servlet is used to 'catch' URL's of the form www.mysite.com and redirects to the wicket app. All my BookmarkablePageLinks are constructed assuming the 'content' context. I can change that so they work from www.mysite.com but then when the pages with www.mysite.com/content/blah... are visited those same links do not work. -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Saturday, 8 May 2010 10:53 AM To: users@wicket.apache.org Subject: Re: Any solution for the context problem with the relative links of BookmarkablePageLink? That wasn't a problem - it was someone configuring the proxy incorrectly. What (specifically) are you encountering? -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 7, 2010 at 7:44 PM, Chris Colman chr...@stepaheadsoftware.comwrote: I was just wondering if there has been any developments on the problem outlined in this post because I'm having the same problem but wanted to avoid the Index link solution: http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative -path-Dilemma-td1933044.html - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Any solution for the context problem with the relative links of BookmarkablePageLink?
On Sun, May 9, 2010 at 5:47 PM, Chris Colman chr...@stepaheadsoftware.comwrote: Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? If you're using the Filter, it should fall through for other requests - allowing them to still be processed. You may have to configure this behavior - it's been a while since I've personally done it. I know that last week I configured a Wicket webapp on /foo when I already had another app on / and they both worked just fine. Two wars - one deployed in tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just worked. -- Jeremy Thomerson http://www.wickettraining.com
Re: Any solution for the context problem with the relative links of BookmarkablePageLink?
I don't think ProxyPass will work (at least it didn't used to) if you try to use the / path, so that might be the trouble you're seeing (if you're seeing any). On Sun, May 9, 2010 at 6:47 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? -- Jeremy Thomerson http://www.wickettraining.com On Sat, May 8, 2010 at 12:40 AM, Chris Colman chr...@stepaheadsoftware.comwrote: I'll explain the problem in detail. I think it's similar to the link I provided but maybe not: I have a site whose home page that is rendered via: www.mysite.com/content/home/pName/pValue but obviously the users will get their via: www.mysite.com I want the home page to be serviced via a forward to www.mysite.com/content/home/pName/pValue so that the search engines don't have to experience a 301 redirect. (where pName/pValue are required parameters that can be passed to any page) I forward via: RequestDispatcher rd = servletContext. getRequestDispatcher(www.mysite.com/content/home/pName/pValue); rd.forward(req, res); I don't mind if all subsequent pages a user visits use the full form of the URL and these full URLs appear in the browser address bar. Eg., www.mysite.com/content/contactUs/pName/pValue www.mysite.com/content/products/pName/pValue www.mysite.com/content/home/pName/pValue The forward works fine but any links on that page don't work because the context of the wicket web app is 'content' - a separate servlet is used to 'catch' URL's of the form www.mysite.com and redirects to the wicket app. All my BookmarkablePageLinks are constructed assuming the 'content' context. I can change that so they work from www.mysite.com but then when the pages with www.mysite.com/content/blah... are visited those same links do not work. -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Saturday, 8 May 2010 10:53 AM To: users@wicket.apache.org Subject: Re: Any solution for the context problem with the relative links of BookmarkablePageLink? That wasn't a problem - it was someone configuring the proxy incorrectly. What (specifically) are you encountering? -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 7, 2010 at 7:44 PM, Chris Colman chr...@stepaheadsoftware.comwrote: I was just wondering if there has been any developments on the problem outlined in this post because I'm having the same problem but wanted to avoid the Index link solution: http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative -path-Dilemma-td1933044.html - 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 - 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: Any solution for the context problem with the relative links of BookmarkablePageLink?
Using the word 'context' was probably misleading on my part. In servlet containers context=app. What I was talking about was the first 'path' element after the domain name, Eg., content in www.mysite.com/content In this case I'm talking about a single app but I set up multiple different URL patterns in the web.xml of that app to direct different patterns to different filters/sevlets. I have a virtual host and all the filters/servlets are under that virtual host and all desployed via a single .war Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? If you're using the Filter, it should fall through for other requests - allowing them to still be processed. You may have to configure this behavior - it's been a while since I've personally done it. I know that last week I configured a Wicket webapp on /foo when I already had another app on / and they both worked just fine. Two wars - one deployed in tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just worked. -- Jeremy Thomerson http://www.wickettraining.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Any solution for the context problem with the relative links of BookmarkablePageLink?
Should still work. If you're using the filter, the idea is that it will only respond to the URLs that it recognizes, and will pass other requests down the chain. -- Jeremy Thomerson http://www.wickettraining.com On Sun, May 9, 2010 at 8:48 PM, Chris Colman chr...@stepaheadsoftware.comwrote: Using the word 'context' was probably misleading on my part. In servlet containers context=app. What I was talking about was the first 'path' element after the domain name, Eg., content in www.mysite.com/content In this case I'm talking about a single app but I set up multiple different URL patterns in the web.xml of that app to direct different patterns to different filters/sevlets. I have a virtual host and all the filters/servlets are under that virtual host and all desployed via a single .war Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? If you're using the Filter, it should fall through for other requests - allowing them to still be processed. You may have to configure this behavior - it's been a while since I've personally done it. I know that last week I configured a Wicket webapp on /foo when I already had another app on / and they both worked just fine. Two wars - one deployed in tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just worked. -- Jeremy Thomerson http://www.wickettraining.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Any solution for the context problem with the relative links of BookmarkablePageLink?
Oh, of course! Sorry I was mistakenly assuming we'd use /* which would match everything but if we use the non wild card / then that will only do an exact match and other URLs with /content etc., will still be able to match their own separate patterns and redirect to their appropriate filters/sevlets. -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Monday, 10 May 2010 12:23 PM To: users@wicket.apache.org Subject: Re: Any solution for the context problem with the relative links of BookmarkablePageLink? Should still work. If you're using the filter, the idea is that it will only respond to the URLs that it recognizes, and will pass other requests down the chain. -- Jeremy Thomerson http://www.wickettraining.com On Sun, May 9, 2010 at 8:48 PM, Chris Colman chr...@stepaheadsoftware.comwrote: Using the word 'context' was probably misleading on my part. In servlet containers context=app. What I was talking about was the first 'path' element after the domain name, Eg., content in www.mysite.com/content In this case I'm talking about a single app but I set up multiple different URL patterns in the web.xml of that app to direct different patterns to different filters/sevlets. I have a virtual host and all the filters/servlets are under that virtual host and all desployed via a single .war Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? If you're using the Filter, it should fall through for other requests - allowing them to still be processed. You may have to configure this behavior - it's been a while since I've personally done it. I know that last week I configured a Wicket webapp on /foo when I already had another app on / and they both worked just fine. Two wars - one deployed in tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just worked. -- Jeremy Thomerson http://www.wickettraining.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: Any solution for the context problem with the relative links of BookmarkablePageLink?
you would use /*, wicket lets urls that it cannot map fallthrough and be handled as usual. additionally wicketfilter has some context params that lets you specify ignore masks, see the source/javadocs. -igor On Sun, May 9, 2010 at 8:22 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Oh, of course! Sorry I was mistakenly assuming we'd use /* which would match everything but if we use the non wild card / then that will only do an exact match and other URLs with /content etc., will still be able to match their own separate patterns and redirect to their appropriate filters/sevlets. -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Monday, 10 May 2010 12:23 PM To: users@wicket.apache.org Subject: Re: Any solution for the context problem with the relative links of BookmarkablePageLink? Should still work. If you're using the filter, the idea is that it will only respond to the URLs that it recognizes, and will pass other requests down the chain. -- Jeremy Thomerson http://www.wickettraining.com On Sun, May 9, 2010 at 8:48 PM, Chris Colman chr...@stepaheadsoftware.comwrote: Using the word 'context' was probably misleading on my part. In servlet containers context=app. What I was talking about was the first 'path' element after the domain name, Eg., content in www.mysite.com/content In this case I'm talking about a single app but I set up multiple different URL patterns in the web.xml of that app to direct different patterns to different filters/sevlets. I have a virtual host and all the filters/servlets are under that virtual host and all desployed via a single .war Is your servlet container listening directly to port 80? Yes. It's pure tomcat - not behind Apache Webserver. If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? I have quite a few non wicket servlets for things like commands and web services and each, including wicket, have their own unique context so that they can all operate peacefully together under. If I mount the wicket app on / will that then pick up request for all the other contexts or is there a way to mount wicket at / and still have other contexts mapping to different servlets? If you're using the Filter, it should fall through for other requests - allowing them to still be processed. You may have to configure this behavior - it's been a while since I've personally done it. I know that last week I configured a Wicket webapp on /foo when I already had another app on / and they both worked just fine. Two wars - one deployed in tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just worked. -- Jeremy Thomerson http://www.wickettraining.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Any solution for the context problem with the relative links of BookmarkablePageLink?
Is your servlet container listening directly to port 80? If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite). Otherwise, can you have your app mounted on /? -- Jeremy Thomerson http://www.wickettraining.com On Sat, May 8, 2010 at 12:40 AM, Chris Colman chr...@stepaheadsoftware.comwrote: I'll explain the problem in detail. I think it's similar to the link I provided but maybe not: I have a site whose home page that is rendered via: www.mysite.com/content/home/pName/pValue but obviously the users will get their via: www.mysite.com I want the home page to be serviced via a forward to www.mysite.com/content/home/pName/pValue so that the search engines don't have to experience a 301 redirect. (where pName/pValue are required parameters that can be passed to any page) I forward via: RequestDispatcher rd = servletContext. getRequestDispatcher(www.mysite.com/content/home/pName/pValue); rd.forward(req, res); I don't mind if all subsequent pages a user visits use the full form of the URL and these full URLs appear in the browser address bar. Eg., www.mysite.com/content/contactUs/pName/pValue www.mysite.com/content/products/pName/pValue www.mysite.com/content/home/pName/pValue The forward works fine but any links on that page don't work because the context of the wicket web app is 'content' - a separate servlet is used to 'catch' URL's of the form www.mysite.com and redirects to the wicket app. All my BookmarkablePageLinks are constructed assuming the 'content' context. I can change that so they work from www.mysite.com but then when the pages with www.mysite.com/content/blah... are visited those same links do not work. -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Saturday, 8 May 2010 10:53 AM To: users@wicket.apache.org Subject: Re: Any solution for the context problem with the relative links of BookmarkablePageLink? That wasn't a problem - it was someone configuring the proxy incorrectly. What (specifically) are you encountering? -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 7, 2010 at 7:44 PM, Chris Colman chr...@stepaheadsoftware.comwrote: I was just wondering if there has been any developments on the problem outlined in this post because I'm having the same problem but wanted to avoid the Index link solution: http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative -path-Dilemma-td1933044.html - 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
Any solution for the context problem with the relative links of BookmarkablePageLink?
I was just wondering if there has been any developments on the problem outlined in this post because I'm having the same problem but wanted to avoid the Index link solution: http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative -path-Dilemma-td1933044.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Any solution for the context problem with the relative links of BookmarkablePageLink?
That wasn't a problem - it was someone configuring the proxy incorrectly. What (specifically) are you encountering? -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 7, 2010 at 7:44 PM, Chris Colman chr...@stepaheadsoftware.comwrote: I was just wondering if there has been any developments on the problem outlined in this post because I'm having the same problem but wanted to avoid the Index link solution: http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative -path-Dilemma-td1933044.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
