[
https://issues.apache.org/jira/browse/CXF-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778418#action_12778418
]
Daniel Kulp commented on CXF-2542:
----------------------------------
Is there a stack trace for when this occurs in a "real life" scenario. In
theory, when this is called as part of the AttachmentDeserializer stuff, the
Exchange would always be set in the message. Thus, the null check wouldn't
be needed.
I have no problem adding the null checks, but I'm curious as to why it really
is needed in a normal case. :-)
> DelegatingInputStream.close() causes MessageImpl.getContextualProperty throw
> NullPointerException
> -------------------------------------------------------------------------------------------------
>
> Key: CXF-2542
> URL: https://issues.apache.org/jira/browse/CXF-2542
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.4
> Reporter: aaron pieper
> Attachments: CxfBug0.java, stack-trace.txt
>
>
> Parsing AttachmentDeserializer's attachments causes an NPE in
> MessageImpl.getContextualProperty sometimes. This can be fixed by adding a
> null check in MessageImpl's getContextualProperty method.
> This problem exists in 2.2.4, it did not exist in 2.2.2. It was caused by a
> change in DelegatingInputStream's close behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
