[SOA-2670] jBPM JtaDbPersistenceServiceFactory backward incompatility in revision 6859 - JBoss Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 5.1.0.ER6, 5.1.0 GA
Component/s: JBPM - standalone, JBPM - within SOA
Labels:
None
Environment:

SOA 5.1.0 snapshot (post ER5)

Affects:

Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration
Release Notes Text:

Hide
https://issues.jboss.org/browse/SOA-2670

The bean configuration property names have been changed so that they now adhere to JavaBeans conventions. For example, property names of the form:

isTransactionEnabled

are now named:

transactionEnabled

They are still backwards-compatible, so names in the previous format can still be used.

Show
https://issues.jboss.org/browse/SOA-2670 The bean configuration property names have been changed so that they now adhere to JavaBeans conventions. For example, property names of the form: isTransactionEnabled are now named: transactionEnabled They are still backwards-compatible, so names in the previous format can still be used.
Release Notes Docs Status:
Documented as Resolved Issue

Description

The change in JtaDbPersistenceServiceFactory property names from:
isTransactionEnabled
isCurrentSessionEnabled
to:
transactionEnabled
currentSessionEnabled
breaks backward compatibility for configurations which have the old names.

Gliffy Diagrams

Attachments

Activity

People

Assignee:

Julian Coleman

Reporter:

Julian Coleman

Writer:

David Le Sage

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

13/Dec/10 6:40 AM

Updated:

12/Jan/12 6:03 PM

Resolved:

15/Dec/10 6:45 AM