[
https://issues.apache.org/jira/browse/WICKET-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Thomerson updated WICKET-1507:
-------------------------------------
Attachment: WICKET-1507-testcase.patch
I tried writing a test case that would reproduce this so that I could work on a
fix. I could not reproduce with this test case, which I think covers the
described situation. I am testing on TRUNK, which is currently 1.4-SNAPSHOT,
and the issue was reported with 1.3.2, so it might have been fixed between now
and then.
Attached patch is the test case I wrote.
> MarkupCache style/variation/locale support broken
> -------------------------------------------------
>
> Key: WICKET-1507
> URL: https://issues.apache.org/jira/browse/WICKET-1507
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2
> Reporter: Meetesh Karia
> Priority: Critical
> Attachments: WICKET-1507-testcase.patch
>
>
> We're running into a problem with the change made for this issue: WICKET-1370
> Basically, if you have a situation like this where the Login page extends
> DefaultPage and uses <wicket:extend>:
> Login.html
> DefaultPage.html
> DefaultPage_style1.html
> DefaultPage_style2.html
> The markup for DefaultPage will always be based on the first style the site
> is hit with. This is because the location string ("Login.html") hasn't
> changed with the style change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
