Many threads/transactions are reading these beans. I have also set JAWS
to make sure these beans are readonly so that it does not update them on
a commit. I wonder why NotSupported does not work?
Bill
danch wrote:
> How do you use the beans? do you make one method call or many? with
> RequiresNew each call will be a transaction. If you can use commit
> option A for these beans, this might not be too bad anyway.
>
> Bill Burke wrote:
>
>> After a little experimenting, I've found that NotSupported does work for
>> the behaviour I want, but RequiresNew does. Is there any problem doing
>> it in this way?
>>
>> Bill
>>
>> Bill Burke wrote:
>>
>>> I'm running JBoss Final-2.0 on Linux, with Oracle and Container
>>> Managed Persistence with JAWS.
>>>
>>> We have a bunch of global EntityBeans that are "readonly". By this I
>>> mean they are never created or modified.
>>>
>>> EntityBeans are locked if they become a part of a transaction, right?
>>> I want to avoid locking these global "readonly" EntityBeans. Can I do
>>> this by declaring their transaction-attributes to be NotSupported?
>>>
>>> Thanks in advance,
>>>
>>> Bill
>>>
>>>
>>>
>>>
>>> --
>>> --------------------------------------------------------------
>>> To subscribe: [EMAIL PROTECTED]
>>> To unsubscribe: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>> --
>> --------------------------------------------------------------
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
