Don,
Glad to hear that you got this working. Since it sounds like you are using
application-managed EntityManagers, then you should have two choices to get
your PersistenceContext associated with your BMT. As you have found out,
you can start the BMT before creating the EM. This is the easiest,
Michael Dick wrote:
If you lookup the UserTransaction in your Session Bean, then your
approach
should work. I tried making the Feature Pack sample application a BMT
bean
and it seemed to work for me. I can send you the application if you'd
like.
If the transaction is started prior to looki
Don,
One clarification...
On 1/1/07, Don Brady <[EMAIL PROTECTED]> wrote:
This is under WebSphere 6.1.
Are you attempting to use OpenJPA with standard WebSphere 6.1 (ala the
DeveloperWorks article that Roland and I wrote --
http://www-128.ibm.com/developerworks/websphere/techjournal/0612_bar
Hi Don,
On 1/1/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Don,
The short answer is yes, UserTransaction is supposed to work.
On Jan 1, 2007, at 11:52 AM, Don Brady wrote:
> I cannot get UserTransaction to work.
>
> Nothing happens when I commit.
Is the symptom that the commit succeed
Hi Don,
The short answer is yes, UserTransaction is supposed to work.
On Jan 1, 2007, at 11:52 AM, Don Brady wrote:
I cannot get UserTransaction to work.
Nothing happens when I commit.
Is the symptom that the commit succeeds but there is no change in the
database?
This consists of:
-
I cannot get UserTransaction to work.
Nothing happens when I commit.
This consists of:
- Using a JTA datasource
- specifying Bean Managed Transaction rather then CMT on the enclosing
session Bean.
- looking up a UserTransaction with:
UserTransaction userTran = (UserTransaction) initCtx
