Re: [Wicket-user] Autolinkresolver within Panel code
Mind you to create a jira bug report as well. it will help us not to forget things. Thanks. Juergen On 5/14/07, Rüdiger Schulz [EMAIL PROTECTED] wrote: I uploaded a quickstart here: http://www.2rue.de/wicket/wicket-quickstart-autolink.tar.gz In fact, I think the problem would occurr even without using base- and childpages. It's just that the error message on the child page displays the combined markup. .rue 2007/5/14, Juergen Donnerstag [EMAIL PROTECTED]: A quickstart would be great -Juergen On 5/14/07, Rüdiger Schulz [EMAIL PROTECTED] wrote: Hello, I am currently migrating my application from 1.2 to 1.3 Snapshot. So far this went very well. But now I have a little problem: All my pages are subclassed from a common basepage. That page has a Panel with login information and some links. On the basepage-markup, the html of the panel is copied to enable an offline preview for my webdesigner (he can work on the templates from within Dreamweaver). The links have a href attribute, so that offline navigation is possible. This worked well in 1.2. In 1.3, I get a markup error at the start of the link: org.apache.wicket.markup.MarkupException: Expected close tag for div id=loginInfoPanel0 wicket:id=loginInfoPanel The page being reported to have a problem is the subpage (!). Now when I remove the href from the links in the basepage (!), all pages render fine, although the links are still there in the subpage-markups, though outside of wicket:extend. So, in this case it was not that big of a deal, but I think this problem might come again. I think it has something to do with Autolinkresolver trying to generate new links in places where he shouldn't. Is it possible to disable this? Should I file a JIRA for this, maybe with a little quickstart? Or am I expecting too much here anyway? I had a similar problem with reproducing panel code to the base page in 1.2 - so where was that current version of this wicket:preview JavaScript again ;-) -- greetings from Berlin, Rüdiger Schulz www.2rue.de - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- greetings from Berlin, Rüdiger Schulz www.2rue.de - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Autolinkresolver within Panel code
Hello, I am currently migrating my application from 1.2 to 1.3 Snapshot. So far this went very well. But now I have a little problem: All my pages are subclassed from a common basepage. That page has a Panel with login information and some links. On the basepage-markup, the html of the panel is copied to enable an offline preview for my webdesigner (he can work on the templates from within Dreamweaver). The links have a href attribute, so that offline navigation is possible. This worked well in 1.2. In 1.3, I get a markup error at the start of the link: org.apache.wicket.markup.MarkupException: Expected close tag for div id=loginInfoPanel0 wicket:id=loginInfoPanel The page being reported to have a problem is the subpage (!). Now when I remove the href from the links in the basepage (!), all pages render fine, although the links are still there in the subpage-markups, though outside of wicket:extend. So, in this case it was not that big of a deal, but I think this problem might come again. I think it has something to do with Autolinkresolver trying to generate new links in places where he shouldn't. Is it possible to disable this? Should I file a JIRA for this, maybe with a little quickstart? Or am I expecting too much here anyway? I had a similar problem with reproducing panel code to the base page in 1.2 - so where was that current version of this wicket:preview JavaScript again ;-) -- greetings from Berlin, Rüdiger Schulz www.2rue.de - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Autolinkresolver within Panel code
A quickstart would be great -Juergen On 5/14/07, Rüdiger Schulz [EMAIL PROTECTED] wrote: Hello, I am currently migrating my application from 1.2 to 1.3 Snapshot. So far this went very well. But now I have a little problem: All my pages are subclassed from a common basepage. That page has a Panel with login information and some links. On the basepage-markup, the html of the panel is copied to enable an offline preview for my webdesigner (he can work on the templates from within Dreamweaver). The links have a href attribute, so that offline navigation is possible. This worked well in 1.2. In 1.3, I get a markup error at the start of the link: org.apache.wicket.markup.MarkupException: Expected close tag for div id=loginInfoPanel0 wicket:id=loginInfoPanel The page being reported to have a problem is the subpage (!). Now when I remove the href from the links in the basepage (!), all pages render fine, although the links are still there in the subpage-markups, though outside of wicket:extend. So, in this case it was not that big of a deal, but I think this problem might come again. I think it has something to do with Autolinkresolver trying to generate new links in places where he shouldn't. Is it possible to disable this? Should I file a JIRA for this, maybe with a little quickstart? Or am I expecting too much here anyway? I had a similar problem with reproducing panel code to the base page in 1.2 - so where was that current version of this wicket:preview JavaScript again ;-) -- greetings from Berlin, Rüdiger Schulz www.2rue.de - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
