You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ivan Vasilev (JIRA)" <ji...@apache.org> on 2010/09/24 02:20:33 UTC
[jira] Created: (WICKET-3079) Nested fragments markup not found
Nested fragments markup not found
---------------------------------
Key: WICKET-3079
URL: https://issues.apache.org/jira/browse/WICKET-3079
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5-M2.1
Environment: Windows, Jetty 7
Reporter: Ivan Vasilev
I have the following markup:
<body>
<wicket:extend>
<span wicket:id="FragmentA_container"></span>
<wicket:fragment wicket:id="FragmentA">
<span wicket:id="FragmentB_container"></span>
<wicket:fragment wicket:id="FragmentB">
<span wicket:id="child_component">
</wicket:fragment>
</wicket:fragment>
</wicket:extend>
</body>
FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
In this case wicket throws an exception:
Markup not found for Component: [ [Component id = child_component]]
I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3079) Nested fragments markup not found
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Vasilev updated WICKET-3079:
---------------------------------
Attachment: fragments_test.rar
Added modified HelloWorld example, which uses fragments.
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Attachments: fragments_test.rar
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3079) Nested fragments markup not found
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3079.
-----------------------------------
Resolution: Fixed
committed on juergen's behalf
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz, wicket-3079.patch
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3079) Nested fragments markup not found
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917324#action_12917324 ]
Juergen Donnerstag commented on WICKET-3079:
--------------------------------------------
Got a new laptop and and forgot my password. Already sent an email to infra to reset
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (WICKET-3079) Nested fragments markup not found
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reopened WICKET-3079:
-------------------------------------
Ok, close the ticket again when you are able to commit the fix.
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-3079) Nested fragments markup not found
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag reassigned WICKET-3079:
------------------------------------------
Assignee: Juergen Donnerstag
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3079) Nested fragments markup not found
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag updated WICKET-3079:
---------------------------------------
Attachment: wicket-3079.patch
until I have access again
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz, wicket-3079.patch
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3079) Nested fragments markup not found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921013#action_12921013 ]
Hudson commented on WICKET-3079:
--------------------------------
Integrated in Apache Wicket 1.5.x #400 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/400/])
Issue: WICKET-3079
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz, wicket-3079.patch
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3079) Nested fragments markup not found
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3079:
------------------------------------
Attachment: fragments_test.tgz
Attach a quickstart with fixed wicket:ids. The attached by Ivan has some typos.
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3079) Nested fragments markup not found
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917297#action_12917297 ]
Martin Grigorov commented on WICKET-3079:
-----------------------------------------
Juergen, you closed it as "Fixed" for 1.5-M3 but I didn't see any commits related to this. Is it possible that your svn client failed to commit it without you notice it?
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3079) Nested fragments markup not found
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-3079.
----------------------------------------
Fix Version/s: 1.5-M3
Resolution: Fixed
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
> Fix For: 1.5-M3
>
> Attachments: fragments_test.rar, fragments_test.tgz
>
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3079) Nested fragments markup not found
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914350#action_12914350 ]
Juergen Donnerstag commented on WICKET-3079:
--------------------------------------------
Please attach a testcase or quickstart
> Nested fragments markup not found
> ---------------------------------
>
> Key: WICKET-3079
> URL: https://issues.apache.org/jira/browse/WICKET-3079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M2.1
> Environment: Windows, Jetty 7
> Reporter: Ivan Vasilev
> Assignee: Juergen Donnerstag
>
> I have the following markup:
> <body>
> <wicket:extend>
> <span wicket:id="FragmentA_container"></span>
> <wicket:fragment wicket:id="FragmentA">
> <span wicket:id="FragmentB_container"></span>
> <wicket:fragment wicket:id="FragmentB">
> <span wicket:id="child_component">
> </wicket:fragment>
> </wicket:fragment>
> </wicket:extend>
> </body>
> FragmentA is added to the page it has added a child of type FragmentB. Also, FragmentB's markup is defined inside FragmetnA.
> In the Java code, when FragmentB is added to FragmentA, FragmentA is specified as markup provider for FragmentB.
> In this case wicket throws an exception:
> Markup not found for Component: [ [Component id = child_component]]
> I have experienced this behavior in several occasions and I've noticed that if a fragment's markup is defined inside another fragment this exception is thrown. The problem occurs because the Fragment.getMarkup(final Component child) method returns null. This worked in wicket 1.4.9.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.