/[bpel2owfn]/bpel2owfn/manual/2.0.x/bpel2owfn.html
ViewVC logotype

Diff of /bpel2owfn/manual/2.0.x/bpel2owfn.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by nielslohmann, Sun Apr 29 12:04:45 2007 UTC revision 1.3 by nielslohmann, Fri May 11 15:29:16 2007 UTC
# Line 11  About this document: Line 11  About this document:
11    
12  This manual is for GNU BPEL2oWFN, version 2.0.1, a tool translating  This manual is for GNU BPEL2oWFN, version 2.0.1, a tool translating
13  a BPEL process into an open workflow net (oWFN), last  a BPEL process into an open workflow net (oWFN), last
14  updated 28 April 2007.  updated 11 May 2007.
15    
16  Copyright (C) 2005, 2006, 2007 Niels Lohmann  Copyright (C) 2005, 2006, 2007 Niels Lohmann
17    
# Line 59  Up:&nbsp;<a rel="up" accesskey="u" href= Line 59  Up:&nbsp;<a rel="up" accesskey="u" href=
59    
60     <p>This manual is for GNU BPEL2oWFN, version 2.0.1, a tool translating     <p>This manual is for GNU BPEL2oWFN, version 2.0.1, a tool translating
61  a <acronym>BPEL</acronym> process into an open workflow net (<acronym>oWFN</acronym>), last  a <acronym>BPEL</acronym> process into an open workflow net (<acronym>oWFN</acronym>), last
62  updated 28 April 2007.  updated 11 May 2007.
63    
64     <p>Copyright &copy; 2005, 2006, 2007 Niels Lohmann     <p>Copyright &copy; 2005, 2006, 2007 Niels Lohmann
65    
# Line 118  the German Federal Ministry for Educatio Line 118  the German Federal Ministry for Educatio
118  <li><a href="#Invoking-BPEL2oWFN">2.1.2 Additional parameters</a>  <li><a href="#Invoking-BPEL2oWFN">2.1.2 Additional parameters</a>
119  <li><a href="#Invoking-BPEL2oWFN">2.1.3 Output formats</a>  <li><a href="#Invoking-BPEL2oWFN">2.1.3 Output formats</a>
120  </li></ul>  </li></ul>
121  <li><a href="#Invoking-BPEL2oWFN">2.2 Examples</a>  <li><a href="#Invoking-BPEL2oWFN">2.2 Exit Values</a>
122    <li><a href="#Invoking-BPEL2oWFN">2.3 Examples</a>
123  </li></ul>  </li></ul>
124  <li><a name="toc_Warnings-and-Error-Messages" href="#Warnings-and-Error-Messages">3 Warnings and Error Messages</a>  <li><a name="toc_Warnings-and-Error-Messages" href="#Warnings-and-Error-Messages">3 Warnings and Error Messages</a>
125  <li><a name="toc_File-Formats" href="#File-Formats">4 File Formats</a>  <li><a name="toc_File-Formats" href="#File-Formats">4 File Formats</a>
# Line 257  information from Flex and Bison about ho Line 258  information from Flex and Bison about ho
258            <dl>            <dl>
259  <dt><span class="samp">0</span><dd>When errors are found, only display the error code and skip additional  <dt><span class="samp">0</span><dd>When errors are found, only display the error code and skip additional
260  information.  information.
261  <dt><span class="samp">1</span><dd>No debug information, but display warning and error messages.  <dt><span class="samp">1</span><dd>No debug information, but display warning and error messages. Furthermore,
262    detailled information about syntax errors are displayed.
263  <dt><span class="samp">2</span><dd>All messages from <span class="samp">-d1</span>. Additionally, information about the current  <dt><span class="samp">2</span><dd>All messages from <span class="samp">-d1</span>. Additionally, information about the current
264  steps is displayed.  steps is displayed.
265  <dt><span class="samp">3</span><dd>All messages from <span class="samp">-d2</span>. Additionally, the structure of the process is  <dt><span class="samp">3</span><dd>All messages from <span class="samp">-d2</span>. Additionally, the structure of the process is
# Line 475  used, a file with the suffix <span class Line 477  used, a file with the suffix <span class
477            </dl>            </dl>
478       </dl>       </dl>
479    
480    <h3 class="section">2.2 Exit Values</h3>
481    
482         <dl>
483    <dt>0<dd>No error occurred.
484    
485         <br><dt>1<dd>A critical error occured; that is, a fault was detected that makes further processing
486    impossible.
487    
488         <br><dt>2<dd>An input file could not be opened.
489    
490         <br><dt>3<dd>A syntax error in the input <acronym>BPEL</acronym> occurred. The input file cannot be
491    further processed.
492    
493         <br><dt>4<dd>Any other error.
494    </dl>
495    
496  <p><a name="Examples"></a>  <p><a name="Examples"></a>
497    
498  <h3 class="section">2.2 Examples</h3>  <h3 class="section">2.3 Examples</h3>
499    
500  <p>In this section we show some examples how BPEL2oWFN can be  <p>In this section we show some examples how BPEL2oWFN can be invoked. See <a href="#File-Formats">File Formats</a>
501  invoked.  for more examples.
502    
503       <dl>       <dl>
504  <dt><span class="samp">bpel2owfn -i sample.bpel -flola -finfo -o -p reduce</span><dd>  <dt><span class="samp">bpel2owfn -i sample.bpel -flola -finfo -o -p reduce</span><dd>
# Line 564  impossible and terminate GNU BPEL2oWFN i Line 582  impossible and terminate GNU BPEL2oWFN i
582  <span class="file">CubeManagement.bpel</span> and the line number <span class="samp">566</span> of the displayed issue.  <span class="file">CubeManagement.bpel</span> and the line number <span class="samp">566</span> of the displayed issue.
583  The line number might be imprecise; that is, it might deviate up or down a  The line number might be imprecise; that is, it might deviate up or down a
584  few lines. After the line number, the error code is displayed.  few lines. After the line number, the error code is displayed.
585  <span class="samp">W00114</span> stands for a warning with code 114. Further details can be  <span class="samp">W00114</span> stands for a warning with code 114. The detailed description of
586  taken from the table below.  the messages can be suppressed with option <span class="samp">-d0</span>.
587    
588  <p><table summary=""><tr align="left"><th valign="top" width="5%">Code </th><th valign="top" width="18%">Type </th><th valign="top" width="72%">Description  <p>Further details can be taken from the table below.
589    
590  <p><br></th></tr><tr align="left"><td valign="top" width="5%">6 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><table summary=""><tr align="left"><th valign="top" width="5%">Code </th><th valign="top" width="18%">Type </th><th valign="top" width="77%">Description
591    
592    <p><br></th></tr><tr align="left"><td valign="top" width="5%">2 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
593    A <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> processor MUST reject any <acronym>WSDL</acronym> portType definition that includes
594    overloaded operation names.<a rel="footnote" href="#fn-3" name="fnd-3"><sup>3</sup></a>
595    
596    <p><br></td></tr><tr align="left"><td valign="top" width="5%">3 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
597    If the value of <code>exitOnStandardFault</code> of a <code>&lt;scope&gt;</code> or <code>&lt;process&gt;</code>
598    is set to <code>"yes"</code>, then a fault handler that explicitly targets the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym>
599    standard faults MUST NOT be used in that scope.
600    
601    <p><br></td></tr><tr align="left"><td valign="top" width="5%">6 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
602  The <code>&lt;rethrow&gt;</code> activity MUST only be used within a faultHandler (i.e.  The <code>&lt;rethrow&gt;</code> activity MUST only be used within a faultHandler (i.e.
603  <code>&lt;catch&gt;</code> and <code>&lt;catchAll&gt;</code> elements).<a rel="footnote" href="#fn-3" name="fnd-3"><sup>3</sup></a>  <code>&lt;catch&gt;</code> and <code>&lt;catchAll&gt;</code> elements).
604    
605    <p><br></td></tr><tr align="left"><td valign="top" width="5%">5 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
606    If the <code>portType</code> attribute is included for readability, in a <code>&lt;receive&gt;</code>,
607    <code>&lt;reply&gt;</code>, <code>&lt;invoke&gt;</code>, <code>&lt;onEvent&gt;</code> or <code>&lt;onMessage&gt;</code>
608    element, the value of the <code>portType</code> attribute MUST match the <code>portType</code>
609    value implied by the combination of the specified <code>partnerLink</code> and the role
610    implicitly specified by the activity.
611    
612  <p><br></td></tr><tr align="left"><td valign="top" width="5%">7 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">7 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
613  The <code>&lt;compensateScope&gt;</code> activity MUST only be used from within a  The <code>&lt;compensateScope&gt;</code> activity MUST only be used from within a
614  <code>faultHandler</code>, another <code>compensationHandler</code>, or a  <code>faultHandler</code>, another <code>compensationHandler</code>, or a
615  <code>terminationHandler</code>.  <code>terminationHandler</code>.
616    
617  <p><br></td></tr><tr align="left"><td valign="top" width="5%">8 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">8 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
618  The <code>&lt;compensate&gt;</code> activity MUST only be used from within a  The <code>&lt;compensate&gt;</code> activity MUST only be used from within a
619  <code>faultHandler</code>, another <code>compensationHandler</code>, or a  <code>faultHandler</code>, another <code>compensationHandler</code>, or a
620  <code>terminationHandler</code>.  <code>terminationHandler</code>.
621    
622  <p><br></td></tr><tr align="left"><td valign="top" width="5%">15 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">15 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
623  To be instantiated, an executable business process MUST contain at least one  To be instantiated, an executable business process MUST contain at least one
624  <code>&lt;receive&gt;</code> or <code>&lt;pick&gt;</code> activity annotated with a  <code>&lt;receive&gt;</code> or <code>&lt;pick&gt;</code> activity annotated with a
625  <code>createInstance="yes"</code> attribute.  <code>createInstance="yes"</code> attribute.
626    
627  <p><br></td></tr><tr align="left"><td valign="top" width="5%">16 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">16 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
628  A <code>partnerLink</code> MUST specify the <code>myRole</code> or the <code>partnerRole</code>,  A <code>partnerLink</code> MUST specify the <code>myRole</code> or the <code>partnerRole</code>,
629  or both.  or both.
630    
631  <p><br></td></tr><tr align="left"><td valign="top" width="5%">17 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">17 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
632  The <code>initializePartnerRole</code> attribute MUST NOT be used on a partnerLink  The <code>initializePartnerRole</code> attribute MUST NOT be used on a partnerLink
633  that does not have a partner role.  that does not have a partner role.
634    
635  <p><br></td></tr><tr align="left"><td valign="top" width="5%">18 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">18 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
636  The name of a <code>partnerLink</code> MUST be unique among the names of all  The name of a <code>partnerLink</code> MUST be unique among the names of all
637  partnerLinks defined within the same immediately enclosing scope.  partnerLinks defined within the same immediately enclosing scope.
638    
639  <p><br></td></tr><tr align="left"><td valign="top" width="5%">23 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">23 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
640  The name of a variable MUST be unique among the names of all variables defined  The name of a variable MUST be unique among the names of all variables defined
641  within the same immediately enclosing scope.  within the same immediately enclosing scope.
642    
643  <p><br></td></tr><tr align="left"><td valign="top" width="5%">24 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">24 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
644  Variable names are <code>BPELVariableNames</code>, that is, NCNames (as defined in  Variable names are <code>BPELVariableNames</code>, that is, NCNames (as defined in
645  <acronym title="Extensible Markup Lanuage">XML</acronym> Schema specification) but in addition they MUST NOT contain the  <acronym title="Extensible Markup Lanuage">XML</acronym> Schema specification) but in addition they MUST NOT contain the
646  <span class="samp">.</span> character.  <span class="samp">.</span> character.
647    
648  <p><br></td></tr><tr align="left"><td valign="top" width="5%">25 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">25 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
649  The <code>messageType</code>, type or <code>element</code> attributes are used to specify  The <code>messageType</code>, type or <code>element</code> attributes are used to specify
650  the type of a variable. Exactly one of these attributes MUST be used.  the type of a variable. Exactly one of these attributes MUST be used.
651    
652  <p><br></td></tr><tr align="left"><td valign="top" width="5%">44 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">32 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
653    For <code>&lt;assign&gt;</code>, the <code>&lt;from&gt;</code> and <code>&lt;to&gt;</code> element MUST be one
654    of the specified variants.<a rel="footnote" href="#fn-4" name="fnd-4"><sup>4</sup></a>
655    
656    <p><br></td></tr><tr align="left"><td valign="top" width="5%">35 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
657    In the from-spec of the partnerLink variant of <code>&lt;assign&gt;</code> the value
658    <code>"myRole"</code> for attribute <code>endpointReference</code> is only permitted when the
659    partnerLink specifies the attribute <code>myRole</code>.
660    
661    <p><br></td></tr><tr align="left"><td valign="top" width="5%">36 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
662    In the from-spec of the partnerLink variant of <code>&lt;assign&gt;</code> the value
663    <code>"partnerRole"</code> for attribute <code>endpointReference</code> is only permitted
664    when the partnerLink specifies the attribute <code>partnerRole</code>.
665    
666    <p><br></td></tr><tr align="left"><td valign="top" width="5%">37 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
667    In the to-spec of the partnerLink variant of <code>&lt;assign&gt;</code> only partnerLinks
668    are permitted which specify the attribute <code>partnerRole</code>.
669    
670    <p><br></td></tr><tr align="left"><td valign="top" width="5%">44 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
671  The name of a <code>&lt;correlationSet&gt;</code> MUST be unique among the names of all  The name of a <code>&lt;correlationSet&gt;</code> MUST be unique among the names of all
672  <code>&lt;correlationSet&gt;</code> defined within the same immediately enclosing scope.  <code>&lt;correlationSet&gt;</code> defined within the same immediately enclosing scope.
673    
674  <p><br></td></tr><tr align="left"><td valign="top" width="5%">51 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">51 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
675  The <code>inputVariable</code> attribute MUST NOT be used on an <code>Invoke</code>  The <code>inputVariable</code> attribute MUST NOT be used on an <code>Invoke</code>
676  activity that contains <code>&lt;toPart&gt;</code> elements.  activity that contains <code>&lt;toPart&gt;</code> elements.
677    
678  <p><br></td></tr><tr align="left"><td valign="top" width="5%">52 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">52 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
679  The <code>outputVariable</code> attribute MUST NOT be used on an <code>Invoke</code>  The <code>outputVariable</code> attribute MUST NOT be used on an <code>Invoke</code>
680  activity that contains <code>&lt;toPart&gt;</code> elements.  activity that contains <code>&lt;toPart&gt;</code> elements.
681    
682  <p><br></td></tr><tr align="left"><td valign="top" width="5%">55 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">55 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
683  For <code>&lt;receive&gt;</code>, if <code>&lt;fromPart&gt;</code> elements are used on a  For <code>&lt;receive&gt;</code>, if <code>&lt;fromPart&gt;</code> elements are used on a
684  <code>&lt;receive&gt;</code> activity then the variable attribute MUST NOT be used on the  <code>&lt;receive&gt;</code> activity then the variable attribute MUST NOT be used on the
685  same activity.  same activity.
686    
687  <p><br></td></tr><tr align="left"><td valign="top" width="5%">56 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">56 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
688  A &ldquo;start activity&rdquo; is a <code>&lt;receive&gt;</code> or <code>&lt;pick&gt;</code> activity that is  A &ldquo;start activity&rdquo; is a <code>&lt;receive&gt;</code> or <code>&lt;pick&gt;</code> activity that is
689  annotated with a <code>createInstance="yes"</code> attribute. Activities other than  annotated with a <code>createInstance="yes"</code> attribute. Activities other than
690  the following: start activities, <code>&lt;scope&gt;</code>, <code>&lt;flow&gt;</code> and  the following: start activities, <code>&lt;scope&gt;</code>, <code>&lt;flow&gt;</code> and
691  <code>&lt;sequence&gt;</code> MUST NOT be performed prior to or simultaneously with start  <code>&lt;sequence&gt;</code> MUST NOT be performed prior to or simultaneously with start
692  activities.  activities.
693    
694  <p><br></td></tr><tr align="left"><td valign="top" width="5%">57 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">57 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
695  If a process has multiple start activities with correlation sets then all such  If a process has multiple start activities with correlation sets then all such
696  activities MUST share at least one common correlationSet and all common  activities MUST share at least one common correlationSet and all common
697  correlationSets defined on all the activities MUST have the value of the  correlationSets defined on all the activities MUST have the value of the
698  <code>initiate</code> attribute be set to <code>"join"</code>.  <code>initiate</code> attribute be set to <code>"join"</code>.
699    
700  <p><br></td></tr><tr align="left"><td valign="top" width="5%">59 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">59 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
701  For <code>&lt;reply&gt;</code>, if <code>&lt;toPart&gt;</code> elements are used on a <code>&lt;reply&gt;</code>  For <code>&lt;reply&gt;</code>, if <code>&lt;toPart&gt;</code> elements are used on a <code>&lt;reply&gt;</code>
702  activity then the <code>variable</code> attribute MUST NOT be used on the same  activity then the <code>variable</code> attribute MUST NOT be used on the same
703  activity.  activity.
704    
705  <p><br></td></tr><tr align="left"><td valign="top" width="5%">62 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">62 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
706  If <code>&lt;pick&gt;</code> has a <code>createInstance</code> attribute with a value of  If <code>&lt;pick&gt;</code> has a <code>createInstance</code> attribute with a value of
707  <span class="samp">yes</span>, the events in the <code>&lt;pick&gt;</code> MUST all be <code>&lt;onMessage&gt;</code>  <span class="samp">yes</span>, the events in the <code>&lt;pick&gt;</code> MUST all be <code>&lt;onMessage&gt;</code>
708  events.  events.
709    
710  <p><br></td></tr><tr align="left"><td valign="top" width="5%">63 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">63 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
711  The semantics of the <code>&lt;onMessage&gt;</code> event are identical to a  The semantics of the <code>&lt;onMessage&gt;</code> event are identical to a
712  <code>&lt;receive&gt;</code> activity regarding the optional nature of the <code>variable</code>  <code>&lt;receive&gt;</code> activity regarding the optional nature of the <code>variable</code>
713  attribute or <code>&lt;fromPart&gt;</code> elements, if <code>&lt;fromPart&gt;</code> elements on an  attribute or <code>&lt;fromPart&gt;</code> elements, if <code>&lt;fromPart&gt;</code> elements on an
714  activity then the variable attribute MUST NOT be used on the same activity  activity then the variable attribute MUST NOT be used on the same activity
715  (see SA00055).  (see SA00055).
716    
717  <p><br></td></tr><tr align="left"><td valign="top" width="5%">64 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">64 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
718  For <code>&lt;flow&gt;</code>, a declared link's name MUST be unique among all  For <code>&lt;flow&gt;</code>, a declared link's name MUST be unique among all
719  <code>&lt;link&gt;</code> names defined within the same immediately enclosing  <code>&lt;link&gt;</code> names defined within the same immediately enclosing
720  <code>&lt;flow&gt;</code>.  <code>&lt;flow&gt;</code>.
721    
722  <p><br></td></tr><tr align="left"><td valign="top" width="5%">65 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">65 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
723  The value of the <code>linkName</code> attribute of <code>&lt;source&gt;</code> or  The value of the <code>linkName</code> attribute of <code>&lt;source&gt;</code> or
724  <code>&lt;target&gt;</code> MUST be the name of a <code>&lt;link&gt;</code> declared in an enclosing  <code>&lt;target&gt;</code> MUST be the name of a <code>&lt;link&gt;</code> declared in an enclosing
725  <code>&lt;flow&gt;</code> activity.  <code>&lt;flow&gt;</code> activity.
726    
727  <p><br></td></tr><tr align="left"><td valign="top" width="5%">66 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">66 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
728  Every link declared within a <code>&lt;flow&gt;</code> activity MUST have exactly one  Every link declared within a <code>&lt;flow&gt;</code> activity MUST have exactly one
729  activity within the <code>&lt;flow&gt;</code> as its source and exactly one activity within  activity within the <code>&lt;flow&gt;</code> as its source and exactly one activity within
730  the <code>&lt;flow&gt;</code> as its target.  the <code>&lt;flow&gt;</code> as its target.
731    
732  <p><br></td></tr><tr align="left"><td valign="top" width="5%">67 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">67 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
733  Two different links MUST NOT share the same source and target activities; that  Two different links MUST NOT share the same source and target activities; that
734  is, at most one link may be used to connect two activities.  is, at most one link may be used to connect two activities.
735    
736  <p><br></td></tr><tr align="left"><td valign="top" width="5%">68 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">68 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
737  An activity MAY declare itself to be the source of one or more links by  An activity MAY declare itself to be the source of one or more links by
738  including one or more <code>&lt;source&gt;</code> elements. Each <code>&lt;source&gt;</code>  including one or more <code>&lt;source&gt;</code> elements. Each <code>&lt;source&gt;</code>
739  element MUST use a distinct link name.  element MUST use a distinct link name.
740    
741  <p><br></td></tr><tr align="left"><td valign="top" width="5%">69 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">69 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
742  An activity MAY declare itself to be the target of one or more links by  An activity MAY declare itself to be the target of one or more links by
743  including one or more <code>&lt;target&gt;</code> elements. Each <code>&lt;target&gt;</code> element  including one or more <code>&lt;target&gt;</code> elements. Each <code>&lt;target&gt;</code> element
744  associated with a given activity MUST use a link name distinct from all other  associated with a given activity MUST use a link name distinct from all other
745  <code>&lt;target&gt;</code> elements at that activity.  <code>&lt;target&gt;</code> elements at that activity.
746    
747  <p><br></td></tr><tr align="left"><td valign="top" width="5%">70 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">70 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
748  A link MUST NOT cross the boundary of a repeatable construct or the  A link MUST NOT cross the boundary of a repeatable construct or the
749  <code>&lt;compensationHandler&gt;</code> element. This means, a link used within a  <code>&lt;compensationHandler&gt;</code> element. This means, a link used within a
750  repeatable construct (<code>&lt;while&gt;</code>, <code>&lt;repeatUntil&gt;</code>, <code>&lt;forEach&gt;</code>,  repeatable construct (<code>&lt;while&gt;</code>, <code>&lt;repeatUntil&gt;</code>, <code>&lt;forEach&gt;</code>,
# Line 698  repeatable construct (<code>&lt;while&gt Line 752  repeatable construct (<code>&lt;while&gt
752  a <code>&lt;flow&gt;</code> that is itself nested inside the repeatable construct or  a <code>&lt;flow&gt;</code> that is itself nested inside the repeatable construct or
753  <code>&lt;compensationHandler&gt;</code>.  <code>&lt;compensationHandler&gt;</code>.
754    
755  <p><br></td></tr><tr align="left"><td valign="top" width="5%">71 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">71 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
756  A link that crosses a <code>&lt;catch&gt;</code>, <code>&lt;catchAll&gt;</code> or  A link that crosses a <code>&lt;catch&gt;</code>, <code>&lt;catchAll&gt;</code> or
757  <code>&lt;terminationHandler&gt;</code> element boundary MUST be outbound only, that is,  <code>&lt;terminationHandler&gt;</code> element boundary MUST be outbound only, that is,
758  it MUST have its source activity within the <code>&lt;faultHandlers&gt;</code> or  it MUST have its source activity within the <code>&lt;faultHandlers&gt;</code> or
759  <code>&lt;terminationHandler&gt;</code>, and its target activity outside of the scope  <code>&lt;terminationHandler&gt;</code>, and its target activity outside of the scope
760  associated with the handler.  associated with the handler.
761    
762  <p><br></td></tr><tr align="left"><td valign="top" width="5%">72 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">72 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
763  A <code>&lt;link&gt;</code> declared in a <code>&lt;flow&gt;</code> MUST NOT create a control cycle,  A <code>&lt;link&gt;</code> declared in a <code>&lt;flow&gt;</code> MUST NOT create a control cycle,
764  that is, the source activity must not have the target activity as a logically  that is, the source activity must not have the target activity as a logically
765  preceding activity.<a rel="footnote" href="#fn-4" name="fnd-4"><sup>4</sup></a>  preceding activity.<a rel="footnote" href="#fn-5" name="fnd-5"><sup>5</sup></a>
766    
767  <p><br></td></tr><tr align="left"><td valign="top" width="5%">73 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">73 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
768  The expression for a join condition MUST be constructed using only Boolean  The expression for a join condition MUST be constructed using only Boolean
769  operators and the activity's incoming links' status values.  operators and the activity's incoming links' status values.
770    
771  <p><br></td></tr><tr align="left"><td valign="top" width="5%">74 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">74 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
772  The expressions in <code>&lt;startCounterValue&gt;</code> and <code>&lt;finalCounterValue&gt;</code>  The expressions in <code>&lt;startCounterValue&gt;</code> and <code>&lt;finalCounterValue&gt;</code>
773  MUST return a TII (meaning they contain at least one character) that can be  MUST return a TII (meaning they contain at least one character) that can be
774  validated as a <code>xsd:unsignedInt</code>. Static analysis MAY be used to detect  validated as a <code>xsd:unsignedInt</code>. Static analysis MAY be used to detect
775  this erroneous situation at design time when possible (for example, when the  this erroneous situation at design time when possible (for example, when the
776  expression is a constant).  expression is a constant).
777    
778  <p><br></td></tr><tr align="left"><td valign="top" width="5%">75 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">75 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
779  For the <code>&lt;forEach&gt;</code> activity, <code>&lt;branches&gt;</code> is an integer value  For the <code>&lt;forEach&gt;</code> activity, <code>&lt;branches&gt;</code> is an integer value
780  expression. Static analysis MAY be used to detect if the integer value is  expression. Static analysis MAY be used to detect if the integer value is
781  larger than the number of directly enclosed activities of <code>&lt;forEach&gt;</code> at  larger than the number of directly enclosed activities of <code>&lt;forEach&gt;</code> at
782  design time when possible (for example, when the branches expression is a  design time when possible (for example, when the branches expression is a
783  constant).  constant).
784    
785  <p><br></td></tr><tr align="left"><td valign="top" width="5%">76 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">76 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
786  For <code>&lt;forEach&gt;</code> the enclosed scope MUST NOT declare a variable with the  For <code>&lt;forEach&gt;</code> the enclosed scope MUST NOT declare a variable with the
787  same name as specified in the <code>counterName</code> attribute of  same name as specified in the <code>counterName</code> attribute of
788  <code>&lt;forEach&gt;</code>.  <code>&lt;forEach&gt;</code>.
789    
790  <p><br></td></tr><tr align="left"><td valign="top" width="5%">77 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">77 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
791  The value of the <code>target</code> attribute on a <code>&lt;compensateScope&gt;</code>  The value of the <code>target</code> attribute on a <code>&lt;compensateScope&gt;</code>
792  activity MUST refer to the name of an immediately enclosed <code>scope</code> of the  activity MUST refer to the name of an immediately enclosed <code>scope</code> of the
793  <code>scope</code> containing the FCT-handler with the <code>&lt;compensateScope&gt;</code>  <code>scope</code> containing the FCT-handler with the <code>&lt;compensateScope&gt;</code>
794  activity. This includes immediately enclosed scopes of an event handler  activity. This includes immediately enclosed scopes of an event handler
795  (<code>&lt;onEvent&gt;</code> or <code>&lt;onAlarm&gt;</code>) associated with the same <code>scope</code>.  (<code>&lt;onEvent&gt;</code> or <code>&lt;onAlarm&gt;</code>) associated with the same <code>scope</code>.
796    
797  <p><br></td></tr><tr align="left"><td valign="top" width="5%">78 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">78 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
798  The <code>target</code> attribute of a <code>&lt;compensateScope&gt;</code> activity MUST refer  The <code>target</code> attribute of a <code>&lt;compensateScope&gt;</code> activity MUST refer
799  to a <code>scope</code> or an <code>invoke</code> activity with a fault handler or  to a <code>scope</code> or an <code>invoke</code> activity with a fault handler or
800  compensation handler.  compensation handler.
801    
802  <p><br></td></tr><tr align="left"><td valign="top" width="5%">79 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">79 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
803  The root <code>scope</code> inside a FCT-handler MUST not have a compensation  The root <code>scope</code> inside a FCT-handler MUST not have a compensation
804  handler.  handler.
805    
806  <p><br></td></tr><tr align="left"><td valign="top" width="5%">80 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">80 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
807  There MUST be at least one <code>&lt;catch&gt;</code> or <code>&lt;catchAll&gt;</code> element within  There MUST be at least one <code>&lt;catch&gt;</code> or <code>&lt;catchAll&gt;</code> element within
808  a <code>&lt;faultHandlers&gt;</code> element.  a <code>&lt;faultHandlers&gt;</code> element.
809    
810  <p><br></td></tr><tr align="left"><td valign="top" width="5%">81 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">81 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
811  For the <code>&lt;catch&gt;</code> construct; to have a defined type associated with the  For the <code>&lt;catch&gt;</code> construct; to have a defined type associated with the
812  fault variable, the <code>faultVariable</code> attribute MUST only be used if either  fault variable, the <code>faultVariable</code> attribute MUST only be used if either
813  the <code>faultMessageType</code> or <code>faultElement</code> attributes, but not both,  the <code>faultMessageType</code> or <code>faultElement</code> attributes, but not both,
814  accompany it. The <code>faultMessageType</code> and <code>faultElement</code> attributes  accompany it. The <code>faultMessageType</code> and <code>faultElement</code> attributes
815  MUST NOT be used unless accompanied by <code>faultVariable</code> attribute.  MUST NOT be used unless accompanied by <code>faultVariable</code> attribute.
816    
817  <p><br></td></tr><tr align="left"><td valign="top" width="5%">82 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">82 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
818  The peer-scope dependency relation MUST NOT include cycles. In other words,  The peer-scope dependency relation MUST NOT include cycles. In other words,
819  <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> forbids a process in which there are peer scopes S1 and S2  <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> forbids a process in which there are peer scopes S1 and S2
820  such that S1 has a peer-scope dependency on S2 and S2 has a peer-scope  such that S1 has a peer-scope dependency on S2 and S2 has a peer-scope
821  dependency on S1.<a rel="footnote" href="#fn-5" name="fnd-5"><sup>5</sup></a>  dependency on S1.<a rel="footnote" href="#fn-6" name="fnd-6"><sup>6</sup></a>
822    
823  <p><br></td></tr><tr align="left"><td valign="top" width="5%">83 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">83 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
824  An event handler MUST contain at least one <code>&lt;onEvent&gt;</code> or  An event handler MUST contain at least one <code>&lt;onEvent&gt;</code> or
825  <code>&lt;onAlarm&gt;</code> element.  <code>&lt;onAlarm&gt;</code> element.
826    
827  <p><br></td></tr><tr align="left"><td valign="top" width="5%">84 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">84 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
828  The <code>partnerLink</code> reference of <code>&lt;onEvent&gt;</code> MUST resolve to a partner  The <code>partnerLink</code> reference of <code>&lt;onEvent&gt;</code> MUST resolve to a partner
829  link declared in the process in the following order: the associated scope  link declared in the process in the following order: the associated scope
830  first and then the ancestor scopes.  first and then the ancestor scopes.
831    
832  <p><br></td></tr><tr align="left"><td valign="top" width="5%">88 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">88 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
833  For <code>&lt;onEvent&gt;</code>, the resolution order of the <code>correlation set</code>(s)  For <code>&lt;onEvent&gt;</code>, the resolution order of the <code>correlation set</code>(s)
834  referenced by <code>&lt;correlation&gt;</code> MUST be first the associated scope and then  referenced by <code>&lt;correlation&gt;</code> MUST be first the associated scope and then
835  the ancestor scopes.  the ancestor scopes.
836    
837  <p><br></td></tr><tr align="left"><td valign="top" width="5%">91 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">91 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
838  A scope with the <code>isolated</code> attribute set to <code>"yes"</code> is called an  A scope with the <code>isolated</code> attribute set to <code>"yes"</code> is called an
839  isolated scope. Isolated scopes MUST NOT contain other isolated scopes.  isolated scope. Isolated scopes MUST NOT contain other isolated scopes.
840    
841  <p><br></td></tr><tr align="left"><td valign="top" width="5%">92 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">92 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
842  Within a scope, the name of all named immediately enclosed scopes MUST be  Within a scope, the name of all named immediately enclosed scopes MUST be
843  unique.  unique.
844    
845  <p><br></td></tr><tr align="left"><td valign="top" width="5%">93 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">93 </td><td valign="top" width="18%">static analysis </td><td valign="top" width="77%">
846  Identical <code>&lt;catch&gt;</code> constructs MUST NOT exist within a  Identical <code>&lt;catch&gt;</code> constructs MUST NOT exist within a
847  <code>&lt;faultHandlers&gt;</code> element.  <code>&lt;faultHandlers&gt;</code> element.
848    
849  <p><br></td></tr><tr align="left"><td valign="top" width="5%">100 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">100 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
850  Either a non-standard element<a rel="footnote" href="#fn-6" name="fnd-6"><sup>6</sup></a> was parsed  Either a non-standard element<a rel="footnote" href="#fn-7" name="fnd-7"><sup>7</sup></a> was parsed
851  or a <acronym>BPEL</acronym> activity was considered as  or a <acronym>BPEL</acronym> activity was considered as
852  misplaced. In the first case, a non-standard element was parsed when the  misplaced. In the first case, a non-standard element was parsed when the
853  parser expected a <acronym>BPEL</acronym> standard activity. Then, a syntax error is  parser expected a <acronym>BPEL</acronym> standard activity. Then, a syntax error is
# Line 807  was skipped, because it was misplaced. A Line 861  was skipped, because it was misplaced. A
861  embedded in a <code>&lt;while&gt;</code> activity without an enclosing <code>&lt;sequence&gt;</code>  embedded in a <code>&lt;while&gt;</code> activity without an enclosing <code>&lt;sequence&gt;</code>
862  activity. In this case, the second activity triggers this message.  activity. In this case, the second activity triggers this message.
863    
864  <p><br></td></tr><tr align="left"><td valign="top" width="5%">101 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">101 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
865  The <code>&lt;partners&gt;</code> construct (only supported by <acronym>BPEL4WS</acronym> 1.1) is skipped due  The <code>&lt;partners&gt;</code> construct (only supported by <acronym>BPEL4WS</acronym> 1.1) is skipped due
866  to a syntax error.  to a syntax error.
867    
868  <p><br></td></tr><tr align="left"><td valign="top" width="5%">102 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">102 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
869  The <code>&lt;to&gt;</code> or <code>&lt;from&gt;</code> construct is skipped due to a syntax error.  The <code>&lt;to&gt;</code> or <code>&lt;from&gt;</code> construct is skipped due to a syntax error.
870    
871  <p><br></td></tr><tr align="left"><td valign="top" width="5%">103 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">103 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
872  The <code>&lt;condition&gt;</code> construct is skipped due to a syntax error.  The <code>&lt;condition&gt;</code> construct is skipped due to a syntax error.
873    
874  <p><br></td></tr><tr align="left"><td valign="top" width="5%">104 </td><td valign="top" width="18%">critical </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">104 </td><td valign="top" width="18%">critical </td><td valign="top" width="77%">
875  When a syntax error occurs, BPEL2oWFN tries to recover and continues parsing the  When a syntax error occurs, BPEL2oWFN tries to recover and continues parsing the
876  input file after skipping the faulty or unknown element. Sometimes, however,  input file after skipping the faulty or unknown element. Sometimes, however,
877  the skipping of activities yields to situations where a further analysis of the  the skipping of activities yields to situations where a further analysis of the
878  <acronym>BPEL</acronym> process is impossible. In this case, the syntax of the process  <acronym>BPEL</acronym> process is impossible. In this case, the syntax of the process
879  has to be fixed or non-standard elements have to be removed or out-commented.  has to be fixed or non-standard elements have to be removed or out-commented.
880    
881  <p><br></td></tr><tr align="left"><td valign="top" width="5%">105 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">105 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
882  When a syntax error occurs, BPEL2oWFN tries to recover and continues parsing the  When a syntax error occurs, BPEL2oWFN tries to recover and continues parsing the
883  input file after skipping the faulty or unknown element. If it is possible to  input file after skipping the faulty or unknown element. If it is possible to
884  continue, the analysis results might be faulty. In this case, the syntax of the  continue, the analysis results might be faulty. In this case, the syntax of the
885  process has to be fixed or non-standard elements have to be removed or  process has to be fixed or non-standard elements have to be removed or
886  out-commented.  out-commented.
887    
888  <p><br></td></tr><tr align="left"><td valign="top" width="5%">106 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">106 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
889  <acronym title="control flow graph">CFG</acronym> analysis detected two receiving activities (i.e., <code>&lt;receive&gt;</code>,  <acronym title="control flow graph">CFG</acronym> analysis detected two receiving activities (i.e., <code>&lt;receive&gt;</code>,
890  <code>&lt;onEvent&gt;</code>, <code>&lt;onMessage&gt;</code>, synchronous <code>&lt;invoke&gt;</code>) that might  <code>&lt;onEvent&gt;</code>, <code>&lt;onMessage&gt;</code>, synchronous <code>&lt;invoke&gt;</code>) that might
891  be activated concurrently and share the same partner link, port type, operation,  be activated concurrently and share the same partner link, port type, operation,
892  and correlation set. When a message is sent to the process, these activities  and correlation set. When a message is sent to the process, these activities
893  are in <i>conflict</i>; that is, it is not defined which activity will receive an  are in <i>conflict</i>; that is, it is not defined which activity will receive an
894  inbound message. At runtime, the standard fault <span class="samp">bpel:conflictingReceive</span>  inbound message. At runtime, the standard fault <span class="samp">bpel:conflictingReceive</span>
895  would be thrown.<a rel="footnote" href="#fn-7" name="fnd-7"><sup>7</sup></a>  would be thrown.<a rel="footnote" href="#fn-8" name="fnd-8"><sup>8</sup></a>
896    
897  <p><br></td></tr><tr align="left"><td valign="top" width="5%">107 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">107 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
898  A mandatory attribute of an activity was not defined. Especially for  A mandatory attribute of an activity was not defined. Especially for
899  communicating activities, the absence of <code>partnerLink</code> and  communicating activities, the absence of <code>partnerLink</code> and
900  <code>operation</code> might hamper the subsequent analysis and Petri net generation.  <code>operation</code> might hamper the subsequent analysis and Petri net generation.
901    
902  <p><br></td></tr><tr align="left"><td valign="top" width="5%">108 </td><td valign="top" width="18%">syntax </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">108 </td><td valign="top" width="18%">syntax </td><td valign="top" width="77%">
903  An attribute was set to a value that violates the attribute's given type. Only  An attribute was set to a value that violates the attribute's given type. Only
904  the types <code>tBoolean</code>, <code>tInitiate</code>, <code>tRoles</code>, and  the types <code>tBoolean</code>, <code>tInitiate</code>, <code>tRoles</code>, and
905  <code>tPattern</code> are checked.  <code>tPattern</code> are checked.
906    
907  <p><br></td></tr><tr align="left"><td valign="top" width="5%">109 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">109 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
908  A variable referenced in an activity was not defined before; that is, no  A variable referenced in an activity was not defined before; that is, no
909  matching <code>&lt;variable&gt;</code> definition was found in a parent scope.  matching <code>&lt;variable&gt;</code> definition was found in a parent scope.
910    
911  <p><br></td></tr><tr align="left"><td valign="top" width="5%">110 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">110 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
912  A partner link referenced in an activity was not defined before; that is, no  A partner link referenced in an activity was not defined before; that is, no
913  matching <code>&lt;partnerLink&gt;</code> definition was found in the process.  matching <code>&lt;partnerLink&gt;</code> definition was found in the process.
914    
915  <p><br></td></tr><tr align="left"><td valign="top" width="5%">111 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">111 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
916  A correlation set referenced in an activity was not defined before; that is, no  A correlation set referenced in an activity was not defined before; that is, no
917  matching <code>&lt;correlationSet&gt;</code> definition was found in a parent scope.  matching <code>&lt;correlationSet&gt;</code> definition was found in a parent scope.
918    
919  <p><br></td></tr><tr align="left"><td valign="top" width="5%">112 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">112 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
920  The <code>&lt;literal&gt;</code> construct is skipped due to a syntax error.  The <code>&lt;literal&gt;</code> construct is skipped due to a syntax error.
921    
922  <p><br></td></tr><tr align="left"><td valign="top" width="5%">113 </td><td valign="top" width="18%">syntax </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">113 </td><td valign="top" width="18%">syntax </td><td valign="top" width="77%">
923  A <acronym>UTF</acronym>-8 character was read in the input file. As BPEL2oWFN's scanner does not  A <acronym>UTF</acronym>-8 character was read in the input file. As BPEL2oWFN's scanner does not
924  support Unicode, all <acronym>UTF</acronym>-8 characters are ignored. This message is only  support Unicode, all <acronym>UTF</acronym>-8 characters are ignored. This message is only
925  displayed when the first <acronym>UTF</acronym>-8 character is read.  displayed when the first <acronym>UTF</acronym>-8 character is read.
926    
927  <p><br></td></tr><tr align="left"><td valign="top" width="5%">114 </td><td valign="top" width="18%">warning </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">114 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
928  <acronym title="control flow graph">CFG</acronym> analysis detected a read access to a variable that was not  <acronym title="control flow graph">CFG</acronym> analysis detected a read access to a variable that was not
929  initialized before. At runtime, the standard fault  initialized before. At runtime, the standard fault
930  <span class="samp">bpel:uninitializedVariable</span> would be thrown.<a rel="footnote" href="#fn-8" name="fnd-8"><sup>8</sup></a>  <span class="samp">bpel:uninitializedVariable</span> would be thrown.<a rel="footnote" href="#fn-9" name="fnd-9"><sup>9</sup></a>
931    
932  <p><br></td></tr><tr align="left"><td valign="top" width="5%">115 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">115 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
933  The process definition defines an abstract process profile, and thus allows  The process definition defines an abstract process profile, and thus allows
934  several &ldquo;opaque&rdquo; constructs. When processing and analyzing an abstract  several &ldquo;opaque&rdquo; constructs. When processing and analyzing an abstract
935  process, BPEL2oWFN might report error messages that where designed for  process, BPEL2oWFN might report error messages that where designed for
936  executable processes, for example missing attributes. Static analysis errors  executable processes, for example missing attributes. Static analysis errors
937  detected in an abstract process are reported as warnings.  detected in an abstract process are reported as warnings.
938    
939  <p><br></td></tr><tr align="left"><td valign="top" width="5%">116 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">116 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
940  An <code>&lt;opaqueActivity&gt;</code> of an abstract process was replaced by an  An <code>&lt;opaqueActivity&gt;</code> of an abstract process is modeled by an <code>&lt;empty&gt;</code> activity.
 <code>&lt;empty&gt;</code> activity.  
941    
942  <p><br></td></tr><tr align="left"><td valign="top" width="5%">117 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">117 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
943  When using the parameter <span class="samp">communicationonly</span>, the occurrence of join  When using the parameter <span class="samp">communicationonly</span>, the occurrence of join
944  failures is not modeled. Thus, any activity is treated as if the  failures is not modeled. Thus, any activity is treated as if the
945  attribute <span class="samp">suppressJoinFailure</span> is set to <span class="samp">yes</span>.<a rel="footnote" href="#fn-9" name="fnd-9"><sup>9</sup></a>  attribute <span class="samp">suppressJoinFailure</span> is set to <span class="samp">yes</span>.<a rel="footnote" href="#fn-10" name="fnd-10"><sup>10</sup></a>
946    
947  <p><br></td></tr><tr align="left"><td valign="top" width="5%">118 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">118 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
948  A user-defined transition condition is ignored and modeled as &ldquo;<i>n</i>-out-of-<i>n</i>&rdquo;  A user-defined transition condition is ignored and modeled as &ldquo;<i>n</i>-out-of-<i>n</i>&rdquo;
949  (<span class="samp">true</span>) instead.  (<span class="samp">true</span>) instead.
950    
951  <p><br></td></tr><tr align="left"><td valign="top" width="5%">119 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">119 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
952  A user-defined transition condition is ignored and modeled as &ldquo;1-out-of-<i>n</i>&rdquo;  A user-defined transition condition is ignored and modeled as &ldquo;1-out-of-<i>n</i>&rdquo;
953  (XOR) instead.  (XOR) instead.
954    
955  <p><br></td></tr><tr align="left"><td valign="top" width="5%">120 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">120 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
956  When using the parameter <span class="samp">communicationonly</span>, the FTC (fault, termination,  When using the parameter <span class="samp">communicationonly</span>, the FTC (fault, termination,
957  and compensation) handlers are not modeled.  and compensation) handlers are not modeled.
958    
959  <p><br></td></tr><tr align="left"><td valign="top" width="5%">121 </td><td valign="top" width="18%">notice </td><td valign="top" width="72%">  <p><br></td></tr><tr align="left"><td valign="top" width="5%">121 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
960  When using the parameter <span class="samp">communicationonly</span>, activities of the negative  When using the parameter <span class="samp">communicationonly</span>, activities of the negative
961  control flow (<code>&lt;exit&gt;</code>, <code>&lt;throw&gt;</code>, <code>&lt;compensate&gt;</code>, and  control flow (<code>&lt;exit&gt;</code>, <code>&lt;throw&gt;</code>, <code>&lt;compensate&gt;</code>, and
962  <code>&lt;compensateScope&gt;</code>) are replaced by an <code>&lt;empty&gt;</code> activity.  <code>&lt;compensateScope&gt;</code>) are replaced by an <code>&lt;empty&gt;</code> activity.
963    
964    <p><br></td></tr><tr align="left"><td valign="top" width="5%">122 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
965    A syntax error in the <acronym>BPEL4Chor</acronym> chorography file occurred.
966    
967    <p><br></td></tr><tr align="left"><td valign="top" width="5%">123 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
968    A syntax error in the <acronym>WSDL</acronym> input file occurred.
969    
970    <p><br></td></tr><tr align="left"><td valign="top" width="5%">124 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
971    An <acronym title="Extensible Markup Lanuage">XML</acronym> Schema element nested in a <acronym>WSDL</acronym> &lt;types&gt; element was ignored. This is
972    usually no problem, as <acronym>WSDL</acronym> <code>&lt;types&gt;</code> are not evaluated in subsequent analysis
973    or translation.
974    
975    <p><br></td></tr><tr align="left"><td valign="top" width="5%">125 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
976    A variable property element was ignored while parsing the input <acronym>WSDL</acronym> file.
977    
978    <p><br></td></tr><tr align="left"><td valign="top" width="5%">126 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
979    A <acronym>WSDL</acronym> <code>&lt;message&gt;</code> referenced in a <acronym>WSDL</acronym> <code>&lt;operation&gt;</code> was not found.
980    
981    <p><br></td></tr><tr align="left"><td valign="top" width="5%">127 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
982    A <acronym>WSDL</acronym> <code>&lt;portType&gt;</code> referenced in a <acronym>WSDL</acronym> <code>&lt;role&gt;</code> was not found.
983    
984    <p><br></td></tr><tr align="left"><td valign="top" width="5%">128 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
985    A <acronym>WSDL</acronym> <code>&lt;operation&gt;</code> referenced in a <acronym>BPEL</acronym> activity was not specified in the
986    input <acronym>WSDL</acronym> file.
987    
988    <p><br></td></tr><tr align="left"><td valign="top" width="5%">129 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
989    A <acronym>WSDL</acronym> <code>&lt;role&gt;</code> of a <code>partnerLinkType</code> referenced by a <code>&lt;partnerLink&gt;</code> was not
990    defined in the specified <code>&lt;partnerLinkType&gt;</code> in the input <acronym>WSDL</acronym> file.
991    
992    <p><br></td></tr><tr align="left"><td valign="top" width="5%">130 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
993    A <acronym>WSDL</acronym> <code>&lt;partnerLinkType&gt;</code> referenced by a <code>&lt;partnerLink&gt;</code> was not specified in
994    the input <acronym>WSDL</acronym> file.
995    
996    <p><br></td></tr><tr align="left"><td valign="top" width="5%">131 </td><td valign="top" width="18%">error </td><td valign="top" width="77%">
997    An activity has neither a <code>name</code> or <code>id</code> attribute and thus can not be linked with a <acronym>BPEL4Chor</acronym> <code>&lt;messageLink&gt;</code>.
998    
999    <p><br></td></tr><tr align="left"><td valign="top" width="5%">132 </td><td valign="top" width="18%">error </td><td valign="top" width="77%">
1000    An activity has neither could not be linked with a <acronym>BPEL4Chor</acronym> <code>&lt;messageLink&gt;</code> using the activity's <code>name</code> or <code>id</code> attribute.
1001    
1002    <p><br></td></tr><tr align="left"><td valign="top" width="5%">133 </td><td valign="top" width="18%">notice </td><td valign="top" width="77%">
1003    An <code>&lt;extensionActivity&gt;</code> is replaced by an <code>&lt;opaqueActivity&gt;</code> (cf. notice 116).
1004    
1005    <p><br></td></tr><tr align="left"><td valign="top" width="5%">134 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
1006    A <acronym>BPEL4Chor</acronym> <code>&lt;participantType&gt;</code> was defined twice.
1007    
1008    <p><br></td></tr><tr align="left"><td valign="top" width="5%">135 </td><td valign="top" width="18%">warning </td><td valign="top" width="77%">
1009    The <code>&lt;participantType&gt;</code> referenced by a <acronym>BPEL4Chor</acronym> <code>&lt;participant&gt;</code> was not found.
1010    
1011    <p><br></td></tr><tr align="left"><td valign="top" width="5%">136 </td><td valign="top" width="18%">error </td><td valign="top" width="77%">
1012    The value of a <code>&lt;forEach&gt;</code>'s attribute <code>id</code> or <code>name</code> does not reference a <acronym>BPEL4Chor</acronym>
1013    <code>&lt;participant&gt;</code> or <code>&lt;participantSet&gt;</code>. Thus, the <code>&lt;forEach&gt;</code> activity is not grounded to the
1014    <acronym>BPEL4Chor</acronym> topology.
1015    
1016    <p><br></td></tr><tr align="left"><td valign="top" width="5%">137 </td><td valign="top" width="18%">error </td><td valign="top" width="77%">
1017    In a <acronym>BPEL4Chor</acronym> topology, no <acronym title="Extensible Markup Lanuage">XML</acronym> namespace was defined for a <code>&lt;participant&gt;</code>. In a
1018    <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> file, the attribute <code>targetNamespace</code> could not to be grounded to a
1019    BPEL4Chor <code>&lt;participant&gt;</code>.
1020    
1021  <br></td></tr></table>  <br></td></tr></table>
1022    
 <!-- @section Exit Values -->  
 <!-- When BPEL2oWFN is invoked and run without any error, the -->  
 <!-- exit value is 0. -->  
 <!-- Please report the occurrence of any exception with numbers 30-50 -->  
 <!-- since it indicates a bug in BPEL2oWFN we would like to fix -->  
 <!-- immediately (see @ref{Reporting Bugs}). -->  
1023  <!--  -->  <!--  -->
1024  <div class="node">  <div class="node">
1025  <p><hr>  <p><hr>
# Line 954  Up:&nbsp;<a rel="up" accesskey="u" href= Line 1058  Up:&nbsp;<a rel="up" accesskey="u" href=
1058    
1059  <pre class="smallexample">      <pre class="smallexample">    
1060       ==============================================================================       ==============================================================================
1061       GNU BPEL2oWFN 2.0.0 reading from file `example.bpel'       GNU BPEL2oWFN 2.0.1 reading from file `example.bpel'
1062       ------------------------------------------------------------------------------       ------------------------------------------------------------------------------
1063       ------------------------------------------------------------------------------       ------------------------------------------------------------------------------
1064       3 activities (2 basic, 1 structured, 0 scopes) + 3 implicit activities       3 activities (2 basic, 1 structured, 0 scopes) + 3 implicit activities
# Line 1119  analysis tools. In this case, we want to Line 1223  analysis tools. In this case, we want to
1223    
1224  <pre class="smallexample">      <pre class="smallexample">    
1225       {       {
1226         generated by: BPEL2oWFN 2.0.0         generated by: BPEL2oWFN 2.0.1
1227         input file:   `example.bpel' (process `exampleprocess')         input file:   `example.bpel' (process `exampleprocess')
1228         invocation:   `bpel2owfn -i example.bpel -m petrinet -p communicationonly -f owfn'         invocation:   `bpel2owfn -i example.bpel -m petrinet -p communicationonly -f owfn'
1229         net size:     |P|=5, |P_in|= 1, |P_out|= 1, |T|=2, |F|=6         net size:     |P|=5, |P_in|= 1, |P_out|= 1, |T|=2, |F|=6
# Line 1156  analysis tools. In this case, we want to Line 1260  analysis tools. In this case, we want to
1260            
1261  </pre>  </pre>
1262  <p>This is finally the <acronym>oWFN</acronym> model of the <acronym>BPEL</acronym> process that can be analyzed by  <p>This is finally the <acronym>oWFN</acronym> model of the <acronym>BPEL</acronym> process that can be analyzed by
1263  Fiona<a rel="footnote" href="#fn-10" name="fnd-10"><sup>10</sup></a>.  Fiona<a rel="footnote" href="#fn-11" name="fnd-11"><sup>11</sup></a>.
1264    
1265  <!--  -->  <!--  -->
1266  <!--  -->  <!--  -->
# Line 1185  integrates seamlessly. Though the gramma Line 1289  integrates seamlessly. Though the gramma
1289  generated parser is very flexible as it allows to process <acronym>BPEL4WS</acronym> 1.1,  generated parser is very flexible as it allows to process <acronym>BPEL4WS</acronym> 1.1,
1290  <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> 2.0, and to some extend <acronym>BPEL4WS</acronym> 1.0 processes.  <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> 2.0, and to some extend <acronym>BPEL4WS</acronym> 1.0 processes.
1291    
1292       <p>However, the parser does not support <acronym title="Extensible Markup Lanuage">XML</acronym> namspaces. To       <p>However, the parser does not support <acronym title="Extensible Markup Lanuage">XML</acronym> namespaces. BPEL2oWFN will
1293  this end, <acronym>BPEL</acronym> constructs are only recognized if the are either  ignore namespace prefixes and skip all elements that are not explicitly covered
1294  unprefixed or using the prefix <span class="samp">bpws:</span>. Any other elements are skipped  by the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> 2.0, <acronym>BPEL4WS</acronym> 1.2 or <acronym>WSDL</acronym> 1.1 specification,
1295  by the parser of BPEL2oWFN. Nevertheless, processes that use such elements might be  respectively. Nevertheless, skipping elements are reported as syntax error
1296  rejected with a syntax error message (cf. warning message [W00104]).  message (cf. warning message [W00104]).
1297    
1298       <p>As a solution, try removing or commenting non-standard elements, and remove any       <p>As a solution, try removing or commenting non-standard elements.
 namespace prefixed from <acronym>BPEL</acronym> elements.  
1299    
1300       <li><b>I validated my process using an <acronym title="Extensible Markup Lanuage">XML</acronym> validator. Why does       <li><b>I validated my process using an <acronym title="Extensible Markup Lanuage">XML</acronym> validator. Why does
1301  BPEL2oWFN still reports syntax errors?</b>  BPEL2oWFN still reports syntax errors?</b>
1302    
1303       <p>Well, because there <i>are</i> such errors. Many <acronym>BPEL</acronym> editors generate       <p>Well, because there <i>are</i> such errors. Many <acronym>BPEL</acronym> editors generate
1304  invalid <acronym>BPEL</acronym>. Even the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> specification contained  invalid <acronym>BPEL</acronym>. Even the official <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> 2.0 specification contains
1305  processes with syntax errors for a long time. Furthermore, a lot of syntax errors  processes with syntax errors. Furthermore, a lot of syntax errors
1306  cannot be covered with <acronym title="XML Schema Definition">XSD</acronym> (XML Schema Definition) validation. Even if  cannot be covered with <acronym title="XML Schema Definition">XSD</acronym> (XML Schema Definition) validation. Even if
1307  the considered process run on existing engines, BPEL2oWFN might reject it, as  the considered process run on existing engines, BPEL2oWFN might reject it, as
1308  it stubbornly follows the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> specification.  it stubbornly follows the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> specification.
# Line 1713  to permit their use in free software. Line 1816  to permit their use in free software.
1816  static analysis messages are taken from Appendix B of the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym>  static analysis messages are taken from Appendix B of the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym>
1817  specification.</p>  specification.</p>
1818    
1819  <p class="footnote"><small>[<a name="fn-4" href="#fnd-4">4</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>  <p class="footnote"><small>[<a name="fn-4" href="#fnd-4">4</a>]</small> The specification describes all allowed
1820    combinations of elements and attributes in from- and to-specifications.</p>
1821    
1822  <p class="footnote"><small>[<a name="fn-5" href="#fnd-5">5</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>  <p class="footnote"><small>[<a name="fn-5" href="#fnd-5">5</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>
1823    
1824  <p class="footnote"><small>[<a name="fn-6" href="#fnd-6">6</a>]</small> All elements  <p class="footnote"><small>[<a name="fn-6" href="#fnd-6">6</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>
1825    
1826    <p class="footnote"><small>[<a name="fn-7" href="#fnd-7">7</a>]</small> All elements
1827  that are not explicitly defined in the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> specification (e.g.,  that are not explicitly defined in the <acronym title="Web Service Business Process Execution Language">WS-BPEL</acronym> specification (e.g.,
1828  elements from other namespaces) are considered as &ldquo;non-standard&rdquo;.</p>  elements from other namespaces) are considered as &ldquo;non-standard&rdquo;.</p>
1829    
 <p class="footnote"><small>[<a name="fn-7" href="#fnd-7">7</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>  
   
1830  <p class="footnote"><small>[<a name="fn-8" href="#fnd-8">8</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>  <p class="footnote"><small>[<a name="fn-8" href="#fnd-8">8</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>
1831    
1832  <p class="footnote"><small>[<a name="fn-9" href="#fnd-9">9</a>]</small> If the  <p class="footnote"><small>[<a name="fn-9" href="#fnd-9">9</a>]</small> This fault can only be detected in mode mode <span class="samp">cfg</span>.</p>
1833    
1834    <p class="footnote"><small>[<a name="fn-10" href="#fnd-10">10</a>]</small> If the
1835  attribute <span class="samp">suppressJoinFailure</span> is not explicitly defined for an  attribute <span class="samp">suppressJoinFailure</span> is not explicitly defined for an
1836  activity, the value is inherited by the parent activity.</p>  activity, the value is inherited by the parent activity.</p>
1837    
1838  <p class="footnote"><small>[<a name="fn-10" href="#fnd-10">10</a>]</small> Fiona is available at <a href="http://www.informatik.hu-berlin.de/top/tools4bpel">http://www.informatik.hu-berlin.de/top/tools4bpel</a>.</p>  <p class="footnote"><small>[<a name="fn-11" href="#fnd-11">11</a>]</small> Fiona is available at <a href="http://www.informatik.hu-berlin.de/top/tools4bpel">http://www.informatik.hu-berlin.de/top/tools4bpel</a>.</p>
1839    
1840  <p><hr></div>  <p><hr></div>
1841    

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26