Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 971284 - EJB2 Entities CMT handling fall back to default for Home methods even if a 'all method' element is added to the deployment descriptor
EJB2 Entities CMT handling fall back to default for Home methods even if a 'a...
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: EAP 6.4.0
Assigned To: Dominik Pospisil
Jan Martiska
Depends On:
  Show dependency treegraph
Reported: 2013-06-06 04:02 EDT by wfink
Modified: 2017-07-25 03:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-03-20 05:53:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description wfink 2013-06-06 04:02:10 EDT
Description of problem:
If the following element is added to the DS
   <container-transaction >
      <method >

The expectation is that ALL methods are executed with a new Tx in CMT.
In opposite to former versions, where this is true, here the Tx fall back to the default which is 'Required'.

This will have unexpected results during Migration.

A possible workaround is to add a extra container-transaction element and specify the <method-intf>LocalHome</method-intf> (RemoteHome should be avoided for different reasons).
But this will be a huge effort if the application contains a big number of such Entities.
Comment 3 Dimitris Andreadis 2013-10-24 14:27:59 EDT
Assigning jpai@redhat.com EJB issues to david.lloyd@redhat.com. Please re-assign to Cheng or others as needed.
Comment 4 Dominik Pospisil 2015-03-20 05:53:23 EDT
Closing as I was not able to reproduce the issue with 6.4.x branch.

Testcase showing <method-name>*</method-name> works for both instance and local home interfaces in CMP as well as BMP beans:


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