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

older

[JBoss JIRA] (JBIDE-12272) Change...

[JBoss JIRA] (JBIDE-10736) Build...

Marek Baluch (JIRA)

Thursday, 6 January 2011 Thu, 6 Jan '11

9:29 a.m.

Show replies by date

Marek Baluch (JIRA)

Thursday, 6 January Thu, 6 Jan

9:33 a.m.

New subject: [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: -------------------------------- Steps to Reproduce: Using the attached project 1) create an assign activity using simpleIn as <from> and moderateOut as <to>

...

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

9:33 a.m.

New subject: [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: -------------------------------- Attachment: test_project.zip

...

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

Friday, 7 January Fri, 7 Jan

3:49 a.m.

New subject: [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.

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Attachments: test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

3:51 a.m.

New subject: [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: -------------------------------- Attachment: NPE_stack.txt

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Attachments: NPE_stack.txt, test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Max Rydahl Andersen (JIRA)

Tuesday, 18 January Tue, 18 Jan

6:13 a.m.

New subject: [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... ] Max Rydahl Andersen updated JBIDE-8064: --------------------------------------- Assignee: Robert (Bob) Brodt Fix Version/s: 3.2.x 3.3.x Bob, for you ?

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.x, 3.3.x Attachments: NPE_stack.txt, test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Robert (Bob) Brodt (JIRA)

Wednesday, 19 January Wed, 19 Jan

11:23 a.m.

New subject: [JBoss JIRA] Commented: (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... ] Robert (Bob) Brodt commented on JBIDE-8064: ------------------------------------------- I think this has been fixed with https://issues.jboss.org/browse/JBIDE-8048 - can you retest with a newer build?

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.x, 3.3.x Attachments: NPE_stack.txt, test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

11:44 a.m.

New subject: [JBoss JIRA] Commented: (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 commented on JBIDE-8064: ------------------------------------- Sure.

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.x, 3.3.x Attachments: NPE_stack.txt, test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

2:36 p.m.

New subject: [JBoss JIRA] Commented: (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 commented on JBIDE-8064: ------------------------------------- Retried with JBT 3.2_trunk.2011-01-19_08-51-02-H962. The Initializer dialog is not popping up any more for simple types but it doesn't appear for messages like <message name="moderateRequestMessage"> <part name="moderateRequest" type="tns:complexType"/> </message> either. As long as the part has a 'type' attribute instead of an 'element' attribute the initializer dialog will not appear. These need initialization too though.

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.x, 3.3.x Attachments: NPE_stack.txt, test_project.zip 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).

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Brian Fitzpatrick (JIRA)

Thursday, 24 February Thu, 24 Feb

9:01 a.m.

New subject: [JBoss JIRA] Commented: (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... ] Brian Fitzpatrick commented on JBIDE-8064: ------------------------------------------ Bob, bumped to 3.2.1 for now. If not 3.2.1, should probably go in a 3.3 release or LATER.

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.1, 3.3.x Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Brian Fitzpatrick (JIRA)

9:01 a.m.

New subject: [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... ] Brian Fitzpatrick updated JBIDE-8064: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.1 (was: 3.2.x)

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Robert (Bob) Brodt Fix For: 3.2.1, 3.3.x Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Feng Qian (JIRA)

Monday, 14 March Mon, 14 Mar

3:31 a.m.

New subject: [JBoss JIRA] Commented: (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... ] Feng Qian commented on JBIDE-8064: ---------------------------------- Hi Marek, I have tested this issue on the trunk codes base. No initializer dialog comes out. So based on the latest codes, could you get the NPE error?

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Feng Qian Fix For: 3.2.1, 3.3.x Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Marek Baluch (JIRA)

Tuesday, 15 March Tue, 15 Mar

4:04 a.m.

New subject: [JBoss JIRA] Commented: (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 commented on JBIDE-8064: ------------------------------------- Hi Feng, no I'm not getting the NPE anymore. But it's still the same as before - please see my comment posted on 19/Jan/11 3:36 PM. I retried with 3.3_trunk.2011-03-11_10-09-49-H1759.

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Feng Qian Fix For: 3.2.1, 3.3.x Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Feng Qian (JIRA)

Monday, 25 April Mon, 25 Apr

1:27 a.m.

New subject: [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... ] Feng Qian updated JBIDE-8064: ----------------------------- Fix Version/s: (was: 3.2.1.M1)

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Feng Qian Fix For: 3.3.x Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Feng Qian (JIRA)

Wednesday, 8 June Wed, 8 Jun

3:14 a.m.

New subject: [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... ] Feng Qian updated JBIDE-8064: ----------------------------- Fix Version/s: LATER (was: 3.3.x)

...

Variable initializer does not generate content for messages which use type attribute instead of element to declare the part. ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8064 URL: https://issues.jboss.org/browse/JBIDE-8064 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Marek Baluch Assignee: Feng Qian Fix For: LATER Attachments: NPE_stack.txt, test_project.zip Original Estimate: 0 minutes Remaining Estimate: 0 minutes 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).

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

RH Bugzilla Integration (JIRA)

Friday, 29 June Fri, 29 Jun

4:10 a.m.

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

RH Bugzilla Integration (JIRA)

4:10 a.m.

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

RH Bugzilla Integration (JIRA)

9:04 a.m.

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

4507

days inactive

5047

days old

jbosstools-issues@lists.jboss.org

Manage subscription

17 comments

6 participants

tags (0)

participants (6)

Brian Fitzpatrick (JIRA)
Feng Qian (JIRA)
Marek Baluch (JIRA)
Max Rydahl Andersen (JIRA)
RH Bugzilla Integration (JIRA)
Robert (Bob) Brodt (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

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