Bug 779531 (SOA-1910) - Update API usage docs in the jBPM documentation
Summary: Update API usage docs in the jBPM documentation
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1910
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Rules / jBPM integration
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-02 10:34 UTC by Tom Baeyens
Modified: 2013-05-08 19:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 779532 779533 (view as bug list)
Environment:
Last Closed: 2010-10-01 14:59:06 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1910 0 None None None Never

Description Tom Baeyens 2010-02-02 10:34:34 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: SOA

This section should be rewritten in the DB and validated with tests:

"
4.1.1.  Relationship with the Configuration Framework 
Persistence API operations should be called from inside a jBPM context block. 
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try {
  // Invoke persistence operations here
} finally {
  jbpmContext.close();
}
"

The title should become something like "jBPM API basics".  I believe the user should be presented with the proper usage of the API on the SOA platform:

JbpmContext jbpmContext = JbpmConfiguration.getInstance().createJbpmContext();
try {
  // Invoke persistence operations here
} catch (Exception e) {
  jbpmContext.setRollbackOnly();
} finally {
  jbpmContext.close();
}

The invocation of setRollbackOnly should be validated in transactions where there is no ongoing JTA like e.g. in a web app  transaction, and in transactions where there is an ongoing JTA transaction like with a surrounding ejb that already requires a transaction.  Both situations should be tested with a successful jBPM operation and with a jBPM exception that throws an exception.

Comment 1 Mark Little 2010-02-09 18:12:56 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]



Note You need to log in before you can comment on or make changes to this bug.