You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2010/11/06 19:56:08 UTC
[jira] Created: (WICKET-3150) Autolink already rendered problem
Autolink already rendered problem
---------------------------------
Key: WICKET-3150
URL: https://issues.apache.org/jira/browse/WICKET-3150
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5-M3
Reporter: Martin Grigorov
Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
at org.apache.wicket.Page.componentRendered(Page.java:361)
at org.apache.wicket.Component.rendered(Component.java:2580)
at org.apache.wicket.Component.render_(Component.java:2384)
at org.apache.wicket.Component.render(Component.java:2307)
....
See the attached quickstart.
The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
If I move the content from the panel to the page .html then everything is OK.
To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3150) Autolink already rendered problem
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3150:
------------------------------------
Description:
Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
at org.apache.wicket.Page.componentRendered(Page.java:361)
at org.apache.wicket.Component.rendered(Component.java:2580)
at org.apache.wicket.Component.render_(Component.java:2384)
at org.apache.wicket.Component.render(Component.java:2307)
....
See the attached quickstart.
The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
If I move the content from the panel to the page .html then everything is OK.
Removing *any* of <wicket:link>s in the panel solves the problem.
To reproduce the problem just run TestHomePage.
was:
Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
at org.apache.wicket.Page.componentRendered(Page.java:361)
at org.apache.wicket.Component.rendered(Component.java:2580)
at org.apache.wicket.Component.render_(Component.java:2384)
at org.apache.wicket.Component.render(Component.java:2307)
....
See the attached quickstart.
The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
If I move the content from the panel to the page .html then everything is OK.
To reproduce the problem just run TestHomePage.
> Autolink already rendered problem
> ---------------------------------
>
> Key: WICKET-3150
> URL: https://issues.apache.org/jira/browse/WICKET-3150
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Attachments: wicket-3150.tgz
>
>
> Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
> org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
> at org.apache.wicket.Page.componentRendered(Page.java:361)
> at org.apache.wicket.Component.rendered(Component.java:2580)
> at org.apache.wicket.Component.render_(Component.java:2384)
> at org.apache.wicket.Component.render(Component.java:2307)
> ....
> See the attached quickstart.
> The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
> If I move the content from the panel to the page .html then everything is OK.
> Removing *any* of <wicket:link>s in the panel solves the problem.
> To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3150) Autolink already rendered problem
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3150:
------------------------------------
Fix Version/s: 1.5-M4
> Autolink already rendered problem
> ---------------------------------
>
> Key: WICKET-3150
> URL: https://issues.apache.org/jira/browse/WICKET-3150
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M4
>
> Attachments: wicket-3150.tgz
>
>
> Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
> org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
> at org.apache.wicket.Page.componentRendered(Page.java:361)
> at org.apache.wicket.Component.rendered(Component.java:2580)
> at org.apache.wicket.Component.render_(Component.java:2384)
> at org.apache.wicket.Component.render(Component.java:2307)
> ....
> See the attached quickstart.
> The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
> If I move the content from the panel to the page .html then everything is OK.
> Removing *any* of <wicket:link>s in the panel solves the problem.
> To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3150) Autolink already rendered problem
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3150:
------------------------------------
Attachment: wicket-3150.tgz
> Autolink already rendered problem
> ---------------------------------
>
> Key: WICKET-3150
> URL: https://issues.apache.org/jira/browse/WICKET-3150
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Attachments: wicket-3150.tgz
>
>
> Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
> org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
> at org.apache.wicket.Page.componentRendered(Page.java:361)
> at org.apache.wicket.Component.rendered(Component.java:2580)
> at org.apache.wicket.Component.render_(Component.java:2384)
> at org.apache.wicket.Component.render(Component.java:2307)
> ....
> See the attached quickstart.
> The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
> If I move the content from the panel to the page .html then everything is OK.
> To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3150) Autolink already rendered problem
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-3150.
----------------------------------------
Resolution: Fixed
Assignee: Juergen Donnerstag
> Autolink already rendered problem
> ---------------------------------
>
> Key: WICKET-3150
> URL: https://issues.apache.org/jira/browse/WICKET-3150
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Assignee: Juergen Donnerstag
> Attachments: wicket-3150.tgz
>
>
> Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
> org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
> at org.apache.wicket.Page.componentRendered(Page.java:361)
> at org.apache.wicket.Component.rendered(Component.java:2580)
> at org.apache.wicket.Component.render_(Component.java:2384)
> at org.apache.wicket.Component.render(Component.java:2307)
> ....
> See the attached quickstart.
> The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
> If I move the content from the panel to the page .html then everything is OK.
> Removing *any* of <wicket:link>s in the panel solves the problem.
> To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3150) Autolink already rendered problem
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929853#action_12929853 ]
Hudson commented on WICKET-3150:
--------------------------------
Integrated in Apache Wicket 1.5.x #496 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/496/])
> Autolink already rendered problem
> ---------------------------------
>
> Key: WICKET-3150
> URL: https://issues.apache.org/jira/browse/WICKET-3150
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Martin Grigorov
> Assignee: Juergen Donnerstag
> Attachments: wicket-3150.tgz
>
>
> Trying to migrate my application from 1.4 to 1.5 I experience the following problem:
> org.apache.wicket.markup.MarkupException: The component [AutolinkExternalLink [Component id = _autolink_2]] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.resolver.AutoLinkResolver$AutolinkExternalLink:p:_link11:_autolink_2
> at org.apache.wicket.Page.componentRendered(Page.java:361)
> at org.apache.wicket.Component.rendered(Component.java:2580)
> at org.apache.wicket.Component.render_(Component.java:2384)
> at org.apache.wicket.Component.render(Component.java:2307)
> ....
> See the attached quickstart.
> The content of MyPanel.html is the minimal version of the complete html in our application that reproduces the problem.
> If I move the content from the panel to the page .html then everything is OK.
> Removing *any* of <wicket:link>s in the panel solves the problem.
> To reproduce the problem just run TestHomePage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.