You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2009/12/07 22:00:18 UTC

[jira] Commented: (WICKET-2569) Inheritance layout excludes XML header from output

    [ https://issues.apache.org/jira/browse/WICKET-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787104#action_12787104 ] 

Juergen Donnerstag commented on WICKET-2569:
--------------------------------------------

Wicket should throw an exception since a base clase with <wicket:child> but without a subclass with associated markup containing <wicket:extend> doesn't make sense.

> 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.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.