You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/08/05 19:25:14 UTC
[jira] Resolved: (WICKET-2418) NPE in ResourceReference
[ https://issues.apache.org/jira/browse/WICKET-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2418.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.1
Assignee: Igor Vaynberg
> NPE in ResourceReference
> ------------------------
>
> Key: WICKET-2418
> URL: https://issues.apache.org/jira/browse/WICKET-2418
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.6, 1.3.7, 1.4.0
> Reporter: Stefan Schueffler
> Assignee: Igor Vaynberg
> Fix For: 1.4.1
>
> Attachments: ResourceReference.java.patch, ResourceReference.java.patch
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> Referencing a resource located in a different jar-file (and therefore possibly in a different (parent-)classloader), the ResourceReference fails to add this resource.
> The problem is, that the lookup-and-bind-code after correctly recognizing and adding this PackageResource, falls through to the "normal" resource-add which leads to a NPE in ConcurrentHashMap.
> Fix is trivial, patch is appended.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.