Re: Wicket 1.3 rc1 Relative URLs not working properly
if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy -- View this message in context: http://www.nabble.com/Wicket-1.3-rc1-Relative-URLs-not-working-properly-tf4933399.html#a14150416 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket 1.3 rc1 Relative URLs not working properly
are working perfectly. The only issue I am having is if I have a page this is not mounted as a bookmarkable page the relative paths for my stylesheet and other resources are written out incorrect. Below are examples for the same page if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy -- View this message in context: http://www.nabble.com/Wicket-1.3-rc1-Relative-URLs-not-working-properly-tf4933399.html#a14150416 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket 1.3 rc1 Relative URLs not working properly
The /1 is the web app context. Change it to ../ breaks it on the pages that were working before. One thing I noticed is that if I deploy this to a server which has mod_proxy set up to hide the /1 it seems to work fine. j On Dec 3, 2007 4:10 AM, Johan Compagner [EMAIL PROTECTED] wrote: and /1/ is your servlyet path? what happens if you put ../css/style.css in your markup? Because from the normal page that is the css you want i guess? johan On Dec 2, 2007 11:08 PM, Jeremy Levy [EMAIL PROTECTED] wrote: I just upgraded to Wicket 1.3, it was remarkably smooth. It took about 6 hours overall. Every single thing was explained very well in the migration guide and the things i was looking forward to in 1.3 are working perfectly. The only issue I am having is if I have a page this is not mounted as a bookmarkable page the relative paths for my stylesheet and other resources are written out incorrect. Below are examples for the same page if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy
Re: Wicket 1.3 rc1 Relative URLs not working properly
Sorry for now explaining this properly. My application is deployed within a context of /1. The Wicket filter is mapped to /* of the app context. The first page of the site has url of http://www.somehost.com/1/welcomewhere welcome is mounted as a bookmarkable page. There is a link from the welcome page to a page that isn't bookmarked. The relative path of the CSS is incorrect on the page that isn't mounted as a bookmarkable page. If I make it bookmarkable the path to the CSS its correct. I'm going to create a quickstart project to demonstrate it and log a bug. J On Dec 3, 2007 4:40 PM, Johan Compagner [EMAIL PROTECTED] wrote: huh? i must be missing something here. you say to the first that it works and to the second that it doesn't if /1 is the context then would say the first is broken and the second should work. because the first the url is this: localhost/css/style.css but thats outside of the context. the second it seems to be localhost/1/css/xxx and that seems ok then But it is still strange that those 2 pages give different urls because both should be css/ as far as i see because they are on both on the same level. Please make a jira issue for this johan On Dec 3, 2007 4:08 PM, Jeremy Levy [EMAIL PROTECTED] wrote: The /1 is the web app context. Change it to ../ breaks it on the pages that were working before. One thing I noticed is that if I deploy this to a server which has mod_proxy set up to hide the /1 it seems to work fine. j On Dec 3, 2007 4:10 AM, Johan Compagner [EMAIL PROTECTED] wrote: and /1/ is your servlyet path? what happens if you put ../css/style.css in your markup? Because from the normal page that is the css you want i guess? johan On Dec 2, 2007 11:08 PM, Jeremy Levy [EMAIL PROTECTED] wrote: I just upgraded to Wicket 1.3, it was remarkably smooth. It took about 6 hours overall. Every single thing was explained very well in the migration guide and the things i was looking forward to in 1.3 are working perfectly. The only issue I am having is if I have a page this is not mounted as a bookmarkable page the relative paths for my stylesheet and other resources are written out incorrect. Below are examples for the same page if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy
Re: Wicket 1.3 rc1 Relative URLs not working properly
WICKET-1205 On Dec 3, 2007 5:16 PM, Jeremy Levy [EMAIL PROTECTED] wrote: Sorry for now explaining this properly. My application is deployed within a context of /1. The Wicket filter is mapped to /* of the app context. The first page of the site has url of http://www.somehost.com/1/welcomewhere welcome is mounted as a bookmarkable page. There is a link from the welcome page to a page that isn't bookmarked. The relative path of the CSS is incorrect on the page that isn't mounted as a bookmarkable page. If I make it bookmarkable the path to the CSS its correct. I'm going to create a quickstart project to demonstrate it and log a bug. J On Dec 3, 2007 4:40 PM, Johan Compagner [EMAIL PROTECTED] wrote: huh? i must be missing something here. you say to the first that it works and to the second that it doesn't if /1 is the context then would say the first is broken and the second should work. because the first the url is this: localhost/css/style.css but thats outside of the context. the second it seems to be localhost/1/css/xxx and that seems ok then But it is still strange that those 2 pages give different urls because both should be css/ as far as i see because they are on both on the same level. Please make a jira issue for this johan On Dec 3, 2007 4:08 PM, Jeremy Levy [EMAIL PROTECTED] wrote: The /1 is the web app context. Change it to ../ breaks it on the pages that were working before. One thing I noticed is that if I deploy this to a server which has mod_proxy set up to hide the /1 it seems to work fine. j On Dec 3, 2007 4:10 AM, Johan Compagner [EMAIL PROTECTED] wrote: and /1/ is your servlyet path? what happens if you put ../css/style.css in your markup? Because from the normal page that is the css you want i guess? johan On Dec 2, 2007 11:08 PM, Jeremy Levy [EMAIL PROTECTED] wrote: I just upgraded to Wicket 1.3, it was remarkably smooth. It took about 6 hours overall. Every single thing was explained very well in the migration guide and the things i was looking forward to in 1.3 are working perfectly. The only issue I am having is if I have a page this is not mounted as a bookmarkable page the relative paths for my stylesheet and other resources are written out incorrect. Below are examples for the same page if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy
Wicket 1.3 rc1 Relative URLs not working properly
I just upgraded to Wicket 1.3, it was remarkably smooth. It took about 6 hours overall. Every single thing was explained very well in the migration guide and the things i was looking forward to in 1.3 are working perfectly. The only issue I am having is if I have a page this is not mounted as a bookmarkable page the relative paths for my stylesheet and other resources are written out incorrect. Below are examples for the same page if I mount the page versus not. *Bookmarked Page URL (works):* http://localhost/1/gettingstarted link rel=stylesheet type=text/css href=../css/style.css/ *Nonbookmarked Page URL (doesn't work): * http://localhost/1/?x=5uwbo6kafiblurBY3bq1UEFwOyXneRheYz2FfwYwMiQAxP5GPHI1HfUHBUhydOCe link rel=stylesheet type=text/css href=css/style.css/ *As it's written in my base page html:* link rel=stylesheet type=text/css href=css/style.css/ Is this something I missed in the migration, or a left over, bug maybe? Jeremy
