[JBoss JIRA] Created: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[JBoss JIRA] Created:...

[JBoss JIRA] Created: (JBIDE-6588)...

Jeff DeLong (JIRA)

Friday, 15 October 2010 Fri, 15 Oct '10

9:40 a.m.

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Jeff DeLong I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Jeff DeLong (JIRA)

Friday, 15 October Fri, 15 Oct

9:42 a.m.

New subject: [JBoss JIRA] Updated: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Jeff DeLong updated JBIDE-7351: ------------------------------- Affects Version/s: 3.2.0.M2 Component/s: bpel

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Brian Fitzpatrick (JIRA)

Tuesday, 19 October Tue, 19 Oct

12:47 p.m.

New subject: [JBoss JIRA] Updated: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-7351: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.0.Beta2

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Brian Fitzpatrick (JIRA)

12:47 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-7351: ------------------------------------------ Grid or Bob, any ideas?

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Feng Qian (JIRA)

Wednesday, 20 October Wed, 20 Oct

12:16 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Feng Qian commented on JBIDE-7351: ---------------------------------- Brian, I am looking into this issue. No ideas for now.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

Thursday, 21 October Thu, 21 Oct

5:50 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

6:25 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7351: ------------------------------------------- yeah so...the fix (at least for the validation problems) is to use the XSD-to-XML generator class (MyNewXMLGenerator) to generate "generic" xml documents from the "from-spec" and "to-spec" XSD type definitions, then compare them - if the structures and data types are the same, they should be compatible. This means that the element names of the from/to-spec need to be replaced with something generic (something like <complexElem> and <simpleElem>) and the text nodes would simply be the XSD simple types. Then, "genericizing" the example Jeff had first presented in JBIDE-6748 would yield this: <complexElem> <complexElem> <simpleElem>date</simpleElem> <simpleElem>calculatePolicyQuote</simpleElem> <complexElem> <simpleElem>string</simpleElem> <simpleElem>string</simpleElem> <simpleElem>string</simpleElem> <simpleElem>string</simpleElem> <simpleElem>string</simpleElem> <simpleElem>int</simpleElem> <simpleElem>int</simpleElem> <simpleElem>int</simpleElem> <simpleElem>int</simpleElem> <simpleElem>int</simpleElem> </complexElem> </complexElem> </complexElem> This XML would be compatible with any variable or message part that has the same structure and data types because we're ignoring the element names. There's a small issue with "impedance mismatch" caused by optional elements in either the from-spec or the to-spec, but I think we can work around that.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Feng Qian (JIRA)

Monday, 25 October Mon, 25 Oct

12:56 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Feng Qian commented on JBIDE-7351: ---------------------------------- Yes, Bob. You are right. As long as you work on variable initiallization and have found the way to fix, I re-assign this issue to you.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Feng Qian Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

Friday, 29 October Fri, 29 Oct

11:05 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7351: ------------------------------------------- Jeff, I have checked in some partial fixes for the initialization and assignment compatibility checking, but this only takes care of the problems with BPEL variables. There are still other issues with partnerLinks, properties of variables and endpoint reference assignments (some of these combinations should not even be allowed!) Unless you think these are high priority issues, I'd like to push them off to the next release (after beta2) - please change the "Fix version" for this JIRA accordingly if you're OK with that. This fix was another biggie (which is why it took me so long ;) because I basically had to write my own XSD comparer for the assignment compatibility checking. The previous version of this code simply compared the two java objects for equality. I haven't had time to do a lot of testing (only ran through the various combinations of the PolicyQuote sample schemas) but I hope to be able to write some JUnits with additional schemas from...somewhere - if you have any ideas for sample schemas you'd like to see tested, please let me know. One other thing I'd like to do is add automatic generation of literals for variable initialization (similar to what happens in the Assign Properties). This should be simple enough to do: if the user selects "Fixed Value" from the Initialization tab of the variable Property Sheet, the editor will automatically construct the appropriate XML literal and insert it - sound reasonable?

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Jeff DeLong (JIRA)

Monday, 1 November Mon, 1 Nov

4:49 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-7351: ------------------------------------ Bob, I will download the latest NB and test out the changes you made for initializers. I don't have any other complex schemas to test with (the PolicyQuote seems to have generated enough challenges). Fixed Value Initialization sounds good; if this occurs then the first copy operation should not ask the user if they want to Initialize the variable. Thanks.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

5:13 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7351: ------------------------------------------- Sounds like a plan. Actually, the automatic "variable needs initialization" detection code is broken too :( I'm thinking of taking that variable initialization prompt dialog out altogether and using the "Fixed Value" selection in the "From" combobox to generate an appropriate initializer. The resulting "Fixed Value" XML can then be edited as required; if the user selects a different "To" variable, a new initializer will be generated.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Jeff DeLong (JIRA)

5:47 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-7351: ------------------------------------ Yes, I noticed that as well. I just installed the latest NB, and the initialized variables look fine; but on one of my Assigns, I was not asked to generate an Initializer, and on another, it kept asking me every time I added a Copy but then did not add the initialization copy.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

Thursday, 4 November Thu, 4 Nov

10:34 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Robert (Bob) Brodt (JIRA)

10:34 a.m.

New subject: [JBoss JIRA] Resolved: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt resolved JBIDE-7351. --------------------------------------- Resolution: Done

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

Jeff DeLong (JIRA)

Thursday, 18 November Thu, 18 Nov

3:44 p.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-7351: ------------------------------------ I am testing PolicyQuoteProcess with latest NB. My assign statements were already created in earlier version of editor so they do not have initializers. So I went to each assign and added another copy statement os it would request creation of the Initializer. The worked for the first two assign statements (AssignDataForDrivingRecord and AssignDataForCreditCheck), but not for the last three (which have more complex message schemas). However, when I deleted the entire Assign and re-created it; then the initializer was created appropriately.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

Max Andersen (JIRA)

Tuesday, 23 November Tue, 23 Nov

4:22 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Max Andersen commented on JBIDE-7351: ------------------------------------- is this to be done in B2 or ?

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.Beta2 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

Max Andersen (JIRA)

Wednesday, 24 November Wed, 24 Nov

8:39 a.m.

New subject: [JBoss JIRA] Updated: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-7351: -------------------------------- Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2)

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.CR1 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

Max Andersen (JIRA)

8:39 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Max Andersen commented on JBIDE-7351: ------------------------------------- Assuming this is fixfor CR1 not B2

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.CR1 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

Robert (Bob) Brodt (JIRA)

9:30 a.m.

New subject: [JBoss JIRA] Commented: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7351: ------------------------------------------- Yes, sorry for the late reply. I thought this was resolved but we seem to be finding additional bugs as new scenarios are tested. Also the whole variable initialization thing needs to be thought out.

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://jira.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: 3.2.0.CR1 Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

Robert (Bob) Brodt (JIRA)

Tuesday, 21 December Tue, 21 Dec

3:58 p.m.

New subject: [JBoss JIRA] Updated: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy

[ https://issues.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt updated JBIDE-7351: -------------------------------------- Fix Version/s: LATER (was: 3.2.0.CR1) Moved to LATER

...

General issues with Variable Initialization, Assign, and Copy ------------------------------------------------------------- Key: JBIDE-7351 URL: https://issues.jboss.org/browse/JBIDE-7351 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Reporter: Jeff DeLong Assignee: Robert (Bob) Brodt Fix For: LATER Original Estimate: 0 minutes Remaining Estimate: 0 minutes I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.

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

5590

days inactive

5657

days old

jbosstools-issues@lists.jboss.org

Manage subscription

19 comments

5 participants

tags (0)

participants (5)

Brian Fitzpatrick (JIRA)
Feng Qian (JIRA)
Jeff DeLong (JIRA)
Max Andersen (JIRA)
Robert (Bob) Brodt (JIRA)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy