Actually this requirement has come up quite a bit.
<vendor>
Many of our customers find that GemStone/J's persistent cache is a great way
to achieve this. It is essentially shared memory backed up by hard storage.
You access the cache through JNDI. Think of it like a transactional LDAP.
</vendor>
-Chris.
> -----Original Message-----
> From: Vaishali Narkhede [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, August 06, 1999 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: No persistence for entity bean.
>
> Hi, this may sound weird but I want to have an entity bean without any
> persistence. I do not want them to make session beans as for our next
> iteration those objects are going to be entity beans and will provide
> persistence. But for first iteration, we are not persisting those objects.
> I
> want to have minimum code changes between these two iterations and that is
> why I am asking that can I have entity beans without persistence?
>
> Thanks.
>
> Vaishali Narkhede
>
> Xtra Online
> 301 N Market Street
> Dallas, TX 75202
>
> Phone: (214) 753-4221
> Fax: (214) 753-4001
>
> ==========================================================================
> =
> 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".
