[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=12558666#action_12558666 ] 

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.

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