Women in Technology

Hear us Roar



Article:
  Bean-Managed Transaction Suspension in J2EE
Subject:   Point?
Date:   2005-07-22 09:13:56
From:   hbarua
Response to: Point?

>> This article explains exactly that - how to do >>it when you need it.
Yes it makes sense from that perspective. Thanks for pointing it out.

>>I think it's important for developers to >>understand internal 'kitchen' of framework >>they're using and possible problems/limitations >>it imposes.
Absolutely agree with this.


>>J2EE spec is not a dogma, and looking up TM >>doesn't make your code less portable than say >>using container-specific deployment descriptors.


I didn't say it's a dogma - the nonportability can come about because certain appservers might have restrictions on the methods you can use on the exposed Transaction Manager. As long as it's not a standard one can never be safe in assuming it.

Main Topics Oldest First

Showing messages 1 through 1 of 1.

  • Point?
    2005-07-22 09:44:39  maximdim [View]

    the nonportability can come about because certain appservers might have restrictions on the methods you can use on the exposed Transaction Manager. As long as it's not a standard one can never be safe in assuming it.

    True. You cannot be sure 100% that TM is available and/or behave properly in any possible container (as shown in article for example there is at least one known problem with TM in WLS). But in the majority of cases it's there and works as expected.