[jira] Commented: (WICKET-2418) NPE in ResourceReference

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739564#action_12739564 ] 

Igor Vaynberg commented on WICKET-2418:
---------------------------------------

what null value is causing the npe?

if we do not let it fallthrough then it will not be registered under the locale and style - which may lead to some undesired sideeffects.

this is a more general problem then just the resource laoding. eg if you add a component to the page out of another jar it will not be able to be deserialized because of the same classloader limitation.

i think you will be much better served by setting up your own iclassresolver that knows about the classloader that loads the other jar you are using.

> 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
>         Attachments: 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.