Bug 1145052 - It is not possible to get a UserTransaction object if a scoped-context is used
Summary: It is not possible to get a UserTransaction object if a scoped-context is used
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: David M. Lloyd
QA Contact: Jan Martiska
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 09:44 UTC by Hisanobu Okuda
Modified: 2018-12-09 18:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-30 13:56:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EJBCLIENT-87 0 Major Resolved It is not possible to get a UserTransaction object if a scoped-context is used 2017-08-30 10:35:02 UTC
Red Hat Issue Tracker PRODMGT-473 0 Major Resolved An EJB client must not have a knowledge of the servers infrastructure and names 2017-08-30 10:35:00 UTC

Description Hisanobu Okuda 2014-09-22 09:44:25 UTC 
Description of problem:


If the default way is used to connect the server it is possible to get a reference for a UserTransaction with
EJBClient.getUserTransaction("node-name")
If a scoped-context is used the default environment might be not set or different and the correct UTx object can not be received.

A simple way to use somthing similar to former releases as
InitialContext.lookup("UserTransaction")
might be a good way as there are no JBoss specific classes necessary


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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