You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Guillaume Smet (JIRA)" <ji...@apache.org> on 2014/03/17 10:50:44 UTC

[jira] [Commented] (WICKET-5532) NPE calling PackageResource.getResourceStream() if there is no RequestCycle defined

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

Guillaume Smet commented on WICKET-5532:
----------------------------------------

Hi Martin,

I confirm it's OK with 6.15.0-SNAPSHOT.

Thanks!

> NPE calling PackageResource.getResourceStream() if there is no RequestCycle defined
> -----------------------------------------------------------------------------------
>
>                 Key: WICKET-5532
>                 URL: https://issues.apache.org/jira/browse/WICKET-5532
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.13.0, 6.14.0
>            Reporter: Guillaume Smet
>            Assignee: Martin Grigorov
>             Fix For: 7.0.0, 6.15.0
>
>
> From my email on the list:
> Since the introduction of the ProcessingResourceStream, it's not
> possible to call PackageResource.getResourceStream() anymore if there
> is no RequestCycle defined.
> Typically, we call it in our Application init() to prepare (mostly
> preprocess and cache) a couple of resources before opening the
> application to the public.
> We now have a NPE here:
> https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/resource/PackageResource.java#L496
> This problem was introduced by this commit:
> https://github.com/apache/wicket/commit/29b26ffffdd619f4e2fe86aa2d2b02ff3e1d6017#diff-428db8d5278d2ac567e471efd377c7c7
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)