[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8064) Variable initializer does not generate content for messages which use type attribute instead of element to declare the part.

[ https://issues.jboss.org/browse/JBIDE-8064?page=com.atlassian.jira.plugin... ] Marek Baluch updated JBIDE-8064: -------------------------------- Description: 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). was: If a message is declared the following way: <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 assignment will work anyway. In these cases the variable initializer should not be triggered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira