Variable initializer does not generate content for messages which use type attribute instead of element to declare the part.

If a message has one of the formats bellow then the variable initializer will not generate the init content even when the user chooses yes.

<message name="moderateRequestMessage">
<part name="moderateRequest" type="tns:complexType"/>
</message>

or

<message name="simpleResponseMessage">
<part name="payload" type="xsd:string"/>
</message>

In the second case there's no need to generate any content - the variable initializer should not be triggered. The following case shows why the variable initializer should not be triggered for simple assignments:

If we have the following variables:

<bpel:variable name="simpleIn" messageType="tns:simpleRequestMessage"/>
<bpel:variable name="processVar" type="xsd:string"/>

and attempt the following assignment:

<bpel:assign validate="no" name="assignToLocal">
<bpel:copy>
<bpel:from part="payload" variable="simpleIn"></bpel:from>
<bpel:to variable="processVar"></bpel:to>
</bpel:copy>
</bpel:assign>

we get a NPE in the log (see attachment).