According to JBI specification (version 1.0; page 186/226) the "getContent()"
methode of the "NormalizeMessage" class may return "null" value.
But in the "SourceUtilImpl" class of package "ow2.petals.component.framework.util"
this situation is not checked.
In practice, A usecase based on bc-soap binding component that receives a SOAP
message with an empthy body part (allowed according WS-I Basic profile 2.0 and
other related specifications) will throw a NPE due to a NormalizeMessage with
empty content.
temp fix on branch version : see commit n° 16147=>16148, in tdejean's petals sandbox
folder
According to JBI specification (version 1.0; page 186/226) the "getContent()"
methode of the "NormalizeMessage" class may return "null" value.
But in the "SourceUtilImpl" class of package "ow2.petals.component.framework.util"
this situation is not checked.
In practice, A usecase based on bc-soap binding component that receives a SOAP
message with an empthy body part (allowed according WS-I Basic profile 2.0 and
other related specifications) will throw a NPE due to a NormalizeMessage with
empty content.
temp fix on branch version : see commit n° 16147=>16148, in tdejean's petals sandbox
folder
Environment:
all (?) . use soapui to generate soap message and send it to an internal petals service engine
Mathieu Carrolle added a comment - Thu, 4 Nov 2010 - 12:05:27 +0100 - edited The fix have not to be done in the createDocument(...) method.
It have to be done in method getInMessageAsDocument() and getoutMessageAsDocument().
The fix have not to be done in the createDocument(...) method.
It have to be done in method getInMessageAsDocument() and getoutMessageAsDocument().