Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
We had to go back to beta2 because of this. It just hits us in too many places :-( Ari S. - Original Message - From: Ari Suutari [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 12:55 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java:440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
beta 4 or rc1 will solve this.You can check out the new improved stuff already from svn trunk if you wish.Building a wicket distribution is a matter of mvn package :-)Martijn On 4/10/06, Ari Suutari [EMAIL PROTECTED] wrote: We had to go back to beta2 because of this. It just hits us in too many places :-(Ari S.- Original Message -From: Ari Suutari [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.netSent: Wednesday, April 05, 2006 12:55 PMSubject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Hi, What exactly do you mean. Inheritance for Pages is still supported.There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.ziptrying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java:440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java :189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:775)But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem,there must be another class which is derived from class usingmarkup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones.I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currentlyI just cannot find time for it. Our applications are all quite large so I cannotdirectly post parts of them - because of this I always ask if the problem would already be known before building a simple exampleof the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome.I understand this. If I promise that I'll start making junit test cases about my problems during next summer could youcheck these two problems with the example applicationsI provided :)Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3.Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page.Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Hi, beta 4 or rc1 will solve this. Great ! You can check out the new improved stuff already from svn trunk if you wish. Building a wicket distribution is a matter of mvn package :-) Yes, I know and I used to build our wicket jars locally, but when beta versions started being available I decided to use them instead (because I thought it would be easier to communicate about possible problems if we are working on a known state/version of wicket). Ari S. On 4/10/06, Ari Suutari [EMAIL PROTECTED] wrote: We had to go back to beta2 because of this. It just hits us in too many places :-( Ari S. - Original Message - From: Ari Suutari [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 12:55 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java :440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges( MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java :775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S.
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
True,It is in the plans to release the next version tomorrow evening. This way you can see if it is worth doing it yourself or wait for our build.MartijnOn 4/10/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi,beta 4 or rc1 will solve this.Great !You can check out the new improved stuff already from svn trunk if you wish.Building a wicket distribution is a matter of mvn package :-) Yes, I know and I used to build our wicket jars locally, but when beta versionsstarted being available I decided to use them instead (because I thought it wouldbe easier to communicate about possible problems if we are working ona known state/version of wicket).Ari S.On 4/10/06, Ari Suutari [EMAIL PROTECTED] wrote: We had to go back to beta2 because of this. It just hits us in too many places :-( Ari S. - Original Message - From: Ari Suutari [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 12:55 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java :440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java :248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges( MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream (MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java :775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extendNote that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately noerror message is thrown yet. Its currently only my laptop. I need totest it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test caselike in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote:Hi, We just updates from 1.2 beta2 to beta3 and noticted thatsome our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that thosecomponents are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extendto base panel's html file - after that stuff from derived panel's wicket:head section
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
What exactly do you mean. Inheritance for Pages is still supported. Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java:440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd___ Wicket-user mailing list Wicket-user@lists.sourceforge.net
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Yes, sure. I'll check them both. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java:440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Seems to me that the following bug is a duplicate: http://sourceforge.net/tracker/index.php?func=detailaid=1464309group_id=119783atid=684975 It has a unit test though ;). Sven Yes, sure. I'll check them both. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, What exactly do you mean. Inheritance for Pages is still supported. There is a simple example at http://download.syncrontech.com/public/wicketpageinheritanceproblem.zip trying to view TestExtendedPage2 with 1.2-beta3: Caused by: wicket.WicketRuntimeException: Expected to find wicket:child/ in base markup at wicket.markup.MergedMarkup.merge(MergedMarkup.java:315) at wicket.markup.MergedMarkup.init(MergedMarkup.java:50) at wicket.markup.MarkupCache.checkForMarkupInheritance(MarkupCache.java:440) at wicket.markup.MarkupCache.loadMarkup(MarkupCache.java:248) at wicket.markup.MarkupCache.loadMarkupAndWatchForChanges(MarkupCache.java:312) at wicket.markup.MarkupCache.getMarkup(MarkupCache.java:189) at wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:105) at wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:775) But the same code works perfectly with beta2. It seems that just simple markup inheritance is not eought to trigger the problem, there must be another class which is derived from class using markup inheritance (ie. in the example, TestExtendPage works, TestExtendedPage2 doesn't). Like with the other issue, I always appreciate simple unit test to verify it and to add it to the existing ones. I'm very sorry for not providing these examples as junit test cases. Getting more familiar with junit tests is on my to-do list, but currently I just cannot find time for it. Our applications are all quite large so I cannot directly post parts of them - because of this I always ask if the problem would already be known before building a simple example of the problem. What makes me a little worry (and sad) is that we have plenty of unit tests for headers and inheritance and I don't remember I changed the expected output, but still there are quite some issues poping up with it currently. So, junit tests are more than welcome. I understand this. If I promise that I'll start making junit test cases about my problems during next summer could you check these two problems with the example applications I provided :) Ari S. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There seems to be also problems if wicket:child/ is used in page's html directly ie. in beta2 I was able to use markup inheritance on page level, but not in beta3. Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Wednesday, April 05, 2006 9:41 AM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Thanks. I'll check it out. Juergen On 4/5/06, Ari Suutari [EMAIL PROTECTED] wrote: There is a simple example in http://download.syncrontech.com/public/wicketheadproblem.zip Ari S. - Original Message - From: Juergen Donnerstag [EMAIL PROTECTED] To: wicket-user@lists.sourceforge.net Sent: Tuesday, April 04, 2006 3:02 PM Subject: Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] update from beta2 to beta3 broke wicket:head in context of wicket:extend
Note that wicket:head MUST be before body, /head, wicket:panel, wicket:border and wicket:extend. Unfortunately no error message is thrown yet. Its currently only my laptop. I need to test it further before committing. If that is not the case in your example, please send me a stripped down version of the page and panels etc preferably as junit test case like in src/test Juergen On 4/4/06, Ari Suutari [EMAIL PROTECTED] wrote: Hi, We just updates from 1.2 beta2 to beta3 and noticted that some our components using wicket:head stuff to add things to page's head no longer work. Closer examination shows that those components are also using wicket:extend tags. Things work if we put an empty wicket:extend/wicket:extend to base panel's html file - after that stuff from derived panel's wicket:head section appears on page. Ari S. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
