[
https://issues.apache.org/jira/browse/WICKET-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787949#action_12787949
]
Juergen Donnerstag commented on WICKET-2569:
--------------------------------------------
Which file contains the page/panel information and which the extension. The
base markup contains the page/panel layout and the "inherited" markup the
specific extension. In my opinion it is more logical that the base markup (the
page layout) provides the xml declaration when merging the markups.
> Inheritance layout excludes XML header from output
> --------------------------------------------------
>
> Key: WICKET-2569
> URL: https://issues.apache.org/jira/browse/WICKET-2569
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.7, 1.4.3
> Reporter: Neil Curzon
> Assignee: Juergen Donnerstag
> Attachments: wicket-2569.patch, wicket-2569.tgz
>
>
> When using inheritance layout, if the superclass (Layout class) has an ?xml
> header at the top, it's excluded from the rendering of subclasses, if they
> have an associated html file. If the subclass has no .html file associated
> with it, the ?xml header is preserved in the rendering output.
> To reproduce: Create a SuperPage class extending WebPage. At the top of
> SuperPage.html, put "<?xml version="1.0" encoding="utf-8"?>" . Create two
> subclasses of SuperPage, one with an HTML file and one without. View the sub
> pages. Notice when the one with an HTML file is rendered, the xml header is
> excluded.
> Expected: The ?xml header should always be preserved in the rendered output
> as it's vital to the layout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
