You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/06/26 14:18:44 UTC
[jira] [Resolved] (WICKET-4607) Regression in
PackageResource.internalGetResourceStream if relative package name and
mount path conflicts
[ https://issues.apache.org/jira/browse/WICKET-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4607.
-------------------------------------
Resolution: Won't Fix
This behavior happened to work in 1.5 by chance and wont be supported in 6.x+.
See http://markmail.org/thread/ll4deziqqqqa35mw
> Regression in PackageResource.internalGetResourceStream if relative package name and mount path conflicts
> ---------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4607
> URL: https://issues.apache.org/jira/browse/WICKET-4607
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0-beta2
> Reporter: Rafał Krupiński
> Attachments: guard-regression.zip
>
>
> After changing from 1.5.6 to 6.0.0-beta2 and going to main page:
> Unexpected RuntimeException
> Last cause: Access denied to (static) package resource
> com/hashnot/nbp. See IPackageResourceGuard
> Root cause:
> org.apache.wicket.request.resource.PackageResource$PackageResourceBlockedException:
> Access denied to (static) package resource com/hashnot/nbp. See
> IPackageResourceGuard
> at org.apache.wicket.request.resource.PackageResource.internalGetResourceStream(PackageResource.java:459)
> [snip]
> See attached project
> The problem appears when the application mounts a page under the same name as existing subpackage.
> In case of conflicting mount-path and relative package name the regression is:
> * in 1.5.x linking to X meant linking to mounted page
> * in 6.0 it means linking to package
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira