wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Thomerson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (WICKET-1689) style resources not looked up correctly in markup inheritance
Date Mon, 01 Dec 2008 22:48:44 GMT

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

Jeremy Thomerson commented on WICKET-1689:
------------------------------------------

this was fixed in 1.3.4 and 1.4 - see https://issues.apache.org/jira/browse/WICKET-1507

> style resources not looked up correctly in markup inheritance
> -------------------------------------------------------------
>
>                 Key: WICKET-1689
>                 URL: https://issues.apache.org/jira/browse/WICKET-1689
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>            Reporter: Michael Grinner
>         Attachments: styletest.zip
>
>
> example:
> ContactPage extends TemplatePage
> TemplatePage_style.html
> TemplatePage.html
> ContactPage.html
> works for no style, so TemplatePage.html and ContactPage.html are used.
> if style is set to 'style' in the session, TemplagePage_style.html is not looked up -
components on ContactPage are looked up correctly.
> It does work ok if there is a ContacPage_style.html as well, then TemplatePage_style.html
is looked up and used! this though is neither expected behaviour nor practical.
> probably loadMarkupAndWatchForChanges sees identical ResourceStreams and does not resolve
the <wicket:child> containing markup
> properties, xmls etc. are looked up for all components and style independant whether
higher hierarchy components properties are styled or not 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message