This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 169664 - Provision for user to enter new attribute atomicTxType for the process tag.
Summary: Provision for user to enter new attribute atomicTxType for the process tag.
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-31 20:22 UTC by pvarghese
Modified: 2009-11-08 09:29 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pvarghese 2009-07-31 20:22:13 UTC
In support of the new runtime functionality to start a transaction when the BPEL process is in atomic mode the following
enhancement is required in the BPEL design time. 

Enhancement Details:

Addition of the new optional attribute 'atomicTxType' to the BPEL <process> tag.
This attribute will have the enumerated values {"Supports", "Required"}

* Supports: If the inbound message exchange as an associated transaction context then the bpel atomic mode will execute
with the client transaction, if the inbound message exchange does not have an associated transaction context then the
bpel atomic mode will not create a transaction.
This is the default type supported even if the attribute 'atomicTxType' is not specified but the 'atomic' attribute is
defined.

* Required: If the inbound message exchange as an associated transaction context then the bpel atomic mode will execute
with the client transaction and behave exactly as the Supports type. If the inbound message exchange does not have an
associated transaction context then the bpel atomic mode will create a new transaction to execute the atomic mode.

 BPEL Editor requirements

* The <process> tag property sheet should have an optional attribute named 'atomicTxType' with the values {"N/A",
"Supports", "Required"}

* The attribute will belong to the SUN extension namespace 
"http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Transaction" similar to the "atomic" attribute.

* Selecting either the "Supports" or the "Required" options should generate the attribute in the <process> tag has follows.
      <process
      .....
      xmlns:sxtx="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Transaction"
      sxtx:atomic="yes"
      sxtx:atomicTxType=["Supports"|"Required"]>

* Selecting the "N/A" option removes the attribute.

* Validation is required to prevent the user from selecting the atomicTxType attribute without selecting the atomic 
attribute. Suggestion is the enable the atomicTxType attribute only when if the atomic attribute is selected.
Comment 1 Vladimir Yaroslavskiy 2009-08-12 13:21:30 UTC
done: http://hg-soabi.stc.com/gfesbv211/rev/287669c13554
Comment 2 terrybraun 2009-10-16 00:03:16 UTC
This issue is tested and verified with the GFESB Build of 10/09/09, including NetBeans IDE 6.7.1 (Build 200910061357).

The following design time tests were successfully passed:
1) The <process> property window enforces a value of "Supports" or "Required" for the Atomic Tx Attribute field with 
correct syntax of an "atomicTxType attribute.
2) When the "atomicTxType" attribute is set with values of "Supports" or "Required", the "atomic" is automatically set 
to "yes".
3) Setting the "atomic" attribute value to "no" disables (resets to "N/A") the "atomicTxType" attribute, if it is set.
4) The <process> property window allows "atomicTxType" attribute to be reset by using a "N/A" value in the Atomic Tx 
Attribute field.
5) An invalid value for the "atomicTxType" attribute is caught by validation.
6) The adding of the "atomicTxType" attribute correctly inserts the SUN extension namespace:
   "http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Transaction" into the BPEL namespace list.