[jira] Resolved: (WICKET-1689) style resources not looked up correctly in markup inheritance

["Juergen Donnerstag (JIRA)" <ji...@apache.org>]

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

Juergen Donnerstag resolved WICKET-1689.
----------------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.4-RC2
                   1.3.6
         Assignee: Juergen Donnerstag

see 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
>            Assignee: Juergen Donnerstag
>             Fix For: 1.3.6, 1.4-RC2
>
>         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.