Por default o JBoss 2.4.x vem com a op��o de commit 'A' e no JBoss
3.x o varia entre o tipo 'A' e 'B' .
A op��o 'A' assume-se que o JBoss � o unico a acessar o BD,
A op��o 'B' efetua o cache entre as transa��es, em que o JBoss n�o
assume que � o �nico a acessar o BD. A sincroniza��o EntityBean/BD �
efetuado atrav�s de ejbLoad/ejbStore no inicio/fim de cada transa��o.
Veja o que diz a documenta��o do JBoss
Option A: The container caches the beans state between transactions.
This options assumes that the bean/container is the only one accessing
the persistent data. Therefore the container synchronizes the memory
state from the persistent storage only (via ejbLoad) when absolutely
neccessary (when the state isn't cached yet), that is before the first
business method executes on a found bean or after the bean is passivated
and reactivated to serve another business method. This behaviour is
regardless of wether the business method executes inside or outside a
transaction.
Option B: The container caches the bean between transactions. However,
unlike option A the container does not have exclusive access to the
persistent storage. Therefore, the container will synchronize the memory
state (via ejbLoad) at the beginning of each transaction. Thus business
methods executing in a transaction context don't see much benefit from
the container caching the bean, whereas business methods executing
outside a transaction context (transaction attributes Never,
NotSupported or Supports) access the cached (and invalid) state of the bean.
[]'s
Claudio Miranda
> Alguem sabe como invalidar o cache do Jboss para os EJB CMP? Eu
> preciso invalidar o cache pois algumas altera��es s�o feitas
> diretamente no banco e assim o cache do ejb fica fora de sincronismo
> com o banco.
>
> Alguem pode me ajudar?
>
---------------------------------------------------------------------
Para cancelar a subscri��o, envie mensagem para:
[EMAIL PROTECTED]
Para comandos adicionais, envie mensagem para: [EMAIL PROTECTED]
