You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Anton (JIRA)" <ji...@apache.org> on 2012/07/12 17:08:34 UTC

[jira] [Updated] (WICKET-4654) FragmentMarkupSourcingStrategy doesn't see fragment markup which is declared in subclassed panel.

     [ https://issues.apache.org/jira/browse/WICKET-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton updated WICKET-4654:
--------------------------

    Description: 
Steps to reproduce:
- Create class ParentPanel extending Panel
- Create class ChildPanel extending ParentPanel
- Create fragment in ChildPanel
- launch app
Result:
MarkupNotFoundException: No Markup found for Fragment fragmentDef in providing markup container 

Sample app attached.

  was:
Steps to reproduce:
- Create class ParentPanel extending Panel
- Create class ChildPanel extending ParentPanel
- Create fragment in ChildPanel
- launch app
Result:
MarkupNotFoundException: No Markup found for Fragment fragmentDef in providing markup container 


    
> FragmentMarkupSourcingStrategy doesn't see fragment markup which is declared in subclassed panel.
> -------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4654
>                 URL: https://issues.apache.org/jira/browse/WICKET-4654
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.7
>         Environment: Ubuntu 12.04 x64
> JDK 1.6.0_30
>            Reporter: Anton
>            Priority: Critical
>         Attachments: FragmentInInheritedPanel.zip
>
>
> Steps to reproduce:
> - Create class ParentPanel extending Panel
> - Create class ChildPanel extending ParentPanel
> - Create fragment in ChildPanel
> - launch app
> Result:
> MarkupNotFoundException: No Markup found for Fragment fragmentDef in providing markup container 
> Sample app attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira