Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
I had problems with sourceforge too today. Thanks Ingram, Eelco On 6/28/06, Ingram Chen [EMAIL PROTECTED] wrote: I will post it after sourceforge allow login. On 6/29/06, Eelco Hillenius [EMAIL PROTECTED] wrote: Thanks. Would you mind attaching that to an issue on sourceforge please? Eelco On 6/27/06, Ingram Chen [EMAIL PROTECTED] wrote: Is there any progress on this issue ? I tried Wicket 1.2 + SiteMesh but still out of luck... I create a quick-start to reproduce this problem: The attachment includes (1) a small decorate page src/webapp/decorators/default .jsp, which only add one line header and footer. (2) Index.html includes a DefaultDataTable from wicket-extension. the reason to use DefaultDataTable is just it reproduce page truncation in our production code base. OK, When first visit http://localhost:8081/quickstart, the render is correct. But after navigate pagination link, the page just got truncated ! There are several portions of our code base still require jsp + sitemesh to work probably. I hope this issue can be solved regards ps. I only include sitemesh.jar in the attachment because size limit. the rest of missing jars are: #from Tomcat 5.5 commons-el.jar jasper-compiler-jdt.jar jasper-compiler.jar jasper-runtime.jar servlet-api.jar jsp-api.jar #from wicket wicket-1.2.jar wicket-extensions-1.2.jar #from jetty org.mortbay.jetty.jar #others commons-logging-1.0.4.jar log4j-1.2.13.jar On 11/22/05, Eelco Hillenius [EMAIL PROTECTED] wrote: In case you have a small test project or something, I would be very interested in taking a look at that and see if there's anything we need to do to make Wicket behave better with sitemesh. There has been more interest in it, so we might setup a small project for it too (wicket-stuff). Eelco On 11/21/05, John Evans [EMAIL PROTECTED] wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem. The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh. The problem is that fairly often when I access a wicket-generated page through sitemesh the output appears as if the wicket-generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short. If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845opclick ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Ingram Chen Java [EMAIL PROTECTED] Institue of BioMedical Sciences Academia Sinica Taiwan blog: http://www.javaworld.com.tw/roller/page/ingramchen Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
Thanks. Would you mind attaching that to an issue on sourceforge please? Eelco On 6/27/06, Ingram Chen [EMAIL PROTECTED] wrote: Is there any progress on this issue ? I tried Wicket 1.2 + SiteMesh but still out of luck... I create a quick-start to reproduce this problem: The attachment includes (1) a small decorate page src/webapp/decorators/default .jsp, which only add one line header and footer. (2) Index.html includes a DefaultDataTable from wicket-extension. the reason to use DefaultDataTable is just it reproduce page truncation in our production code base. OK, When first visit http://localhost:8081/quickstart, the render is correct. But after navigate pagination link, the page just got truncated ! There are several portions of our code base still require jsp + sitemesh to work probably. I hope this issue can be solved regards ps. I only include sitemesh.jar in the attachment because size limit. the rest of missing jars are: #from Tomcat 5.5 commons-el.jar jasper-compiler-jdt.jar jasper-compiler.jar jasper-runtime.jar servlet-api.jar jsp-api.jar #from wicket wicket-1.2.jar wicket-extensions-1.2.jar #from jetty org.mortbay.jetty.jar #others commons-logging-1.0.4.jar log4j-1.2.13.jar On 11/22/05, Eelco Hillenius [EMAIL PROTECTED] wrote: In case you have a small test project or something, I would be very interested in taking a look at that and see if there's anything we need to do to make Wicket behave better with sitemesh. There has been more interest in it, so we might setup a small project for it too (wicket-stuff). Eelco On 11/21/05, John Evans [EMAIL PROTECTED] wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem. The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh. The problem is that fairly often when I access a wicket-generated page through sitemesh the output appears as if the wicket-generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short. If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845opclick ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Ingram Chen Java [EMAIL PROTECTED] Institue of BioMedical Sciences Academia Sinica Taiwan blog: http://www.javaworld.com.tw/roller/page/ingramchen Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list
Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
I will post it after sourceforge allow login. On 6/29/06, Eelco Hillenius [EMAIL PROTECTED] wrote: Thanks. Would you mind attaching that to an issue on sourceforge please?Eelco On 6/27/06, Ingram Chen [EMAIL PROTECTED] wrote: Is there any progress on this issue ? I tried Wicket 1.2 + SiteMesh but still out of luck... I create a quick-start to reproduce this problem: The attachment includes (1) a small decorate page src/webapp/decorators/default .jsp, which only add one lineheader and footer. (2) Index.html includes a DefaultDataTable from wicket-extension. the reason to use DefaultDataTable is just it reproduce page truncation in our production code base. OK, When first visit http://localhost:8081/quickstart, the render is correct. But after navigate pagination link, the page just got truncated ! There are several portions of our code base still require jsp + sitemesh to work probably. I hope this issue can be solved regards ps. I only include sitemesh.jar in the attachment because size limit. the rest of missing jars are: #from Tomcat 5.5 commons-el.jar jasper-compiler-jdt.jar jasper-compiler.jar jasper-runtime.jar servlet-api.jar jsp-api.jar #from wicket wicket-1.2.jar wicket-extensions-1.2.jar #from jetty org.mortbay.jetty.jar #others commons-logging-1.0.4.jar log4j-1.2.13.jar On 11/22/05, Eelco Hillenius [EMAIL PROTECTED] wrote: In case you have a small test project or something, I would be very interested in taking a look at that and see if there's anything we need to do to make Wicket behave better with sitemesh. There has been more interest in it, so we might setup a small project for it too (wicket-stuff). Eelco On 11/21/05, John Evans [EMAIL PROTECTED] wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem.The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh.The problem is that fairly often when I access a wicket-generated page through sitemesh the output appears as if the wicket-generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short.If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John --- This SF.Net email is sponsored by the JBoss Inc.Get Certified Today Register for a JBoss Training Course.Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845opclick ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Ingram Chen Java [EMAIL PROTECTED] Institue of BioMedical Sciences Academia Sinica Taiwan blog: http://www.javaworld.com.tw/roller/page/ingramchen Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-userUsing Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user-- Ingram ChenJava [EMAIL
[Wicket-user] Wicket + Sitemesh - Page truncation problem
I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem. The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh. The problem is that fairly often when I access a wicket-generated page through sitemesh the output appears as if the wicket-generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short. If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John
Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
I do believe, that Sitemesh is really not required when using Wicket... since you can inherit page markup via Border, Panel's, and the wicket:head/wicket:head wicket:extendwicket:child // wicket:extend. Doesn't negate that Sitemesh isn't working correctly with your environment though, but when using wicket, unless you have another framework or pages not controlled by wicket, it probably is moot. On Nov 21, 2005, at 8:05 AM, John Evans wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem. The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh. The problem is that fairly often when I access a wicket- generated page through sitemesh the output appears as if the wicket- generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short. If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
That was the issue exactly -- we want to have several applications all branded exactly the same, but my group is only writing this one application (using wicket) On 11/21/05, Andrew Lombardi [EMAIL PROTECTED] wrote: I do believe, that Sitemesh is really not required when usingWicket... since you can inherit page markup via Border, Panel's, and the wicket:head/wicket:head wicket:extendwicket:child //wicket:extend.Doesn't negate that Sitemesh isn't working correctly with yourenvironment though, but when using wicket, unless you have another framework or pages not controlled by wicket, it probably is moot.On Nov 21, 2005, at 8:05 AM, John Evans wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem.The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh.The problem is that fairly often when I access a wicket- generated page through sitemesh the output appears as if the wicket- generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short.If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John---This SF.Net email is sponsored by the JBoss Inc.Get Certified TodayRegister for a JBoss Training Course.Free Certification Examfor All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Wicket + Sitemesh - Page truncation problem
In case you have a small test project or something, I would be very interested in taking a look at that and see if there's anything we need to do to make Wicket behave better with sitemesh. There has been more interest in it, so we might setup a small project for it too (wicket-stuff). Eelco On 11/21/05, John Evans [EMAIL PROTECTED] wrote: I have never used Sitemesh or Wicket on a real project, although I've played with both and they both seem to work exactly as advertised -- now I'm trying to use them both together on a real project for the first time and I'm having a problem. The problem only happens when I'm accessing a wicket-generated page that has a sitemesh decorator applied to it -- everything works fine if I turn off sitemesh or if I access a non-wicket-generated page through sitemesh. The problem is that fairly often when I access a wicket-generated page through sitemesh the output appears as if the wicket-generated page was truncated -- for example if my wicket generated page were this: body 1 2 3 4 5 /body And my decorator was: body decorator:body/ /body Then the output would be something like this: body 1 2 3 /body The sitemesh template always shows up in it's entirety, but the wicket page is cut short. If I do a refresh this will almost always fix it -- I also haven't been able to re-create the problem with one of wicket's bookmarkable pages, so it makes debugging the problem difficult. My guess is that maybe there is a problem with wicket returning the wrong content-length or something -- but it appears to generate the appropriate values when I run it outside of sitemesh. I'm going to try to get my environment set up in a debugger so that I can debug the entire application with source for wicket and sitemesh attached and see if I can track down the problem, but I thought I would post here (and to the sitemesh forums) first and see if anyone had encountered the same or similar problem and already solved it -- or if anyone has any suggestions for where to start. Thanks, - John --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28alloc_id845op=click ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
