You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Michael Elman (JIRA)" <ji...@apache.org> on 2009/09/07 16:26:57 UTC
[jira] Created: (WINK-166) NullPointerException in
ContextAccessor.getContextFromResolver when running from Client
NullPointerException in ContextAccessor.getContextFromResolver when running from Client
---------------------------------------------------------------------------------------
Key: WINK-166
URL: https://issues.apache.org/jira/browse/WINK-166
Project: Wink
Issue Type: Bug
Components: Common
Affects Versions: 0.1
Reporter: Michael Elman
Priority: Critical
Fix For: 0.2
NullPointerException occurs in ContextAccessor.getContextFromResolver when running from Client
This happens since runtimeContext.getHttpHeaders() is always null.
Actually this is incorrect, since it should be populated with request headers.
Currently it's showstopper for some of our clients, so I'm going to apply a hotfix that will check for nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WINK-166) NullPointerException in
ContextAccessor.getContextFromResolver when running from Client
Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Gallardo updated WINK-166:
-------------------------------
Affects Version/s: 0.2
Fix Version/s: (was: 0.2)
Changing release per Michael's suggestion.
> NullPointerException in ContextAccessor.getContextFromResolver when running from Client
> ---------------------------------------------------------------------------------------
>
> Key: WINK-166
> URL: https://issues.apache.org/jira/browse/WINK-166
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 0.1, 0.2
> Reporter: Michael Elman
> Priority: Critical
>
> NullPointerException occurs in ContextAccessor.getContextFromResolver when running from Client
> This happens since runtimeContext.getHttpHeaders() is always null.
> Actually this is incorrect, since it should be populated with request headers.
> Currently it's showstopper for some of our clients, so I'm going to apply a hotfix that will check for nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WINK-166) NullPointerException in
ContextAccessor.getContextFromResolver when running from Client
Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Gallardo resolved WINK-166.
--------------------------------
Resolution: Fixed
Marking this issue as resolved since it doesn't seem to be appearing anymore.
Please re-open if this is still an issue.
> NullPointerException in ContextAccessor.getContextFromResolver when running from Client
> ---------------------------------------------------------------------------------------
>
> Key: WINK-166
> URL: https://issues.apache.org/jira/browse/WINK-166
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 0.1, 1.0
> Reporter: Michael Elman
> Priority: Critical
>
> NullPointerException occurs in ContextAccessor.getContextFromResolver when running from Client
> This happens since runtimeContext.getHttpHeaders() is always null.
> Actually this is incorrect, since it should be populated with request headers.
> Currently it's showstopper for some of our clients, so I'm going to apply a hotfix that will check for nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WINK-166) NullPointerException in
ContextAccessor.getContextFromResolver when running from Client
Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Gallardo closed WINK-166.
------------------------------
> NullPointerException in ContextAccessor.getContextFromResolver when running from Client
> ---------------------------------------------------------------------------------------
>
> Key: WINK-166
> URL: https://issues.apache.org/jira/browse/WINK-166
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 0.1, 1.0
> Reporter: Michael Elman
> Priority: Critical
>
> NullPointerException occurs in ContextAccessor.getContextFromResolver when running from Client
> This happens since runtimeContext.getHttpHeaders() is always null.
> Actually this is incorrect, since it should be populated with request headers.
> Currently it's showstopper for some of our clients, so I'm going to apply a hotfix that will check for nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WINK-166) NullPointerException in
ContextAccessor.getContextFromResolver when running from Client
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752181#action_12752181 ]
Hudson commented on WINK-166:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #133 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/133/])
fix NPE
see []
> NullPointerException in ContextAccessor.getContextFromResolver when running from Client
> ---------------------------------------------------------------------------------------
>
> Key: WINK-166
> URL: https://issues.apache.org/jira/browse/WINK-166
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 0.1
> Reporter: Michael Elman
> Priority: Critical
> Fix For: 0.2
>
>
> NullPointerException occurs in ContextAccessor.getContextFromResolver when running from Client
> This happens since runtimeContext.getHttpHeaders() is always null.
> Actually this is incorrect, since it should be populated with request headers.
> Currently it's showstopper for some of our clients, so I'm going to apply a hotfix that will check for nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.