I think that Jim referred to the restriction that "The TX_BEAN_MANAGED
transaction attribute value must not be mixed with other values of the
transaction attributes [for the same bean]".
It wouldn't be too useful to prohibit mixing the other attributes.
Imre Kifor
Valto Systems
-----Original Message-----
From: William W. Lee <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, March 02, 1999 3:34 PM
Subject: Re: Entity Bean Management
>>
>> And of course EJB currently requires that all methods in a
>>transaction carry the same TX attribute. So, you won't be able to mix
>>TX_REQUIRES with TX_NOT_SUPPORTED within a transaction.
>>
>
>I believe Persistence PowerTier allows for different TX attribute for each
>method, which is a nice feature to have for performance tuning.
>
>Will
>
>-----------------------------------
>William Lee, Chief Technology Officer
>The Theory Center
>28 State Street, 11th Floor
>Boston, MA 02109
>
>1.617.573.5099
>1.617.262.0703 (Fax)
>
>http://www.theorycenter.com
>-----------------------------------
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
