You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/07/07 21:35:05 UTC
[jira] [Commented] (WICKET-5909) Session style is not taken into
account when loading mounted resources.
[ https://issues.apache.org/jira/browse/WICKET-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617237#comment-14617237 ]
ASF subversion and git services commented on WICKET-5909:
---------------------------------------------------------
Commit 5c829c4ac40d95c78010697dd093aceba4b54877 in wicket's branch refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=5c829c4 ]
WICKET-5909 Session style is not taken into account when loading mounted resources.
Rename IStaticCacheableResource#getCacheableResourceStream() to #getResourceStream().
Merge PackageResource#getCacheableResourceStream() and #getResourceStream() by preserving the behavior of #getCacheableResourceStream()
> Session style is not taken into account when loading mounted resources.
> -----------------------------------------------------------------------
>
> Key: WICKET-5909
> URL: https://issues.apache.org/jira/browse/WICKET-5909
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M5, 6.19.0
> Reporter: Sergiy Barlabanov
> Assignee: Andrea Del Bene
> Fix For: 7.0.0
>
> Attachments: style-bug.zip, wicket.patch
>
>
> Session#getStyle is not considered when a mounted package resource is loaded. Wicket loads the default one.
> If the resource is not mounted, everything works fine and Wicket delivers the correct resource file.
> Quickstart is attached. There are two CSS files: styled.css and styled_orange.css. The corresponding package resource is mounted. The session style is set to orange in WicketApplication#newSession. Expected behavior is that styled_orange.css is delivered to a browser. Instead styled.css is delivered.
> There is a workaround: see WorkaroundResourceStreamLocator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)