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

[Robert (Bob) Brodt (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560318#action_12560318 ] 

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.

-- 
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