No, JBoss doesn't support option B.
org.jboss.ejb.plugins.EntityMultiInstanceSynchronizationInterceptor passivates entity
beans for both option B and C (at line 110-130). On the other hand, the specs said "in
option B, the Container caches a 'ready' instance between transaction" (pp. 186), and,
as depicted the object interaction diagram (pp. 210 and 212), entity beans shall not
be passivated in option B. Why? It gives the bean developers a chance to optimize the
database access. This was discussed at
http://www.jboss.org/forums/thread.jsp?forum=66&thread=12462&message=3706295&q=henri#3706295.
-----Original Message-----
> From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Friday, July 19, 2002 10:31 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Please support Option B
>
> Are these guys on crack?
>
> only shit comes out of csiro...
>
> of course we support option B... also the mail is ignorant, option B
> reloads the data after each transaction by definition, using option B
> wouldn't help here. Using smart Option A with notifications would :)
>
> marcf
�� ��^�����)�{(��[�8b�A�zE���&z�
y�!y�ޞm���)��r����[�� z������ٚ�X��X�����^��h�g��X���(�� ~��zw���i����l���q���z���l�X��)ߣ�ۢ� z������
