[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2984) JtaDbPersistenceServiceFactory backward incompatility in revision 6859
[
https://issues.jboss.org/browse/JBPM-2984?page=com.atlassian.jira.plugin....
]
Alejandro Guizar commented on JBPM-2984:
----------------------------------------
Restored the code path in the jBPM configuration parser allowing a property name such as
isFoo to bind an accessor method named setFoo(value). While behavior goes against
JavaBeans guidelines, jBPM has traditionally supported it, perhaps due to misunderstanding
the naming convention.
Contrary to what the description says, setter method names did not change in
JtaDbPersistenceFactory, it was the code used to associate property names to setter
methods.
The regression was introduced by JBPM-2982, an issue resolved in version 3.2.10. This is
why this issue's "Affects Version" field is set to 3.2.10.
JtaDbPersistenceServiceFactory backward incompatility in revision
6859
----------------------------------------------------------------------
Key: JBPM-2984
URL: https://issues.jboss.org/browse/JBPM-2984
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.10
Environment: SOA 5.1.0 snapshot
Reporter: Julian Coleman
Assignee: Alejandro Guizar
Priority: Blocker
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The change in JtaDbPersistenceServiceFactory property names from:
isTransactionEnabled
isCurrentSessionEnabled
to:
transactionEnabled
currentSessionEnabled
breaks backward compatibility for configurations which have the old names.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira