Re: Modelling Read Only Database Tables

[Geoff Lingham]

Hi

Rickard wrote:

> You do not need to do activation/passivation all the time, which are
> potentially very costly operations. I have a bean which does ALOT (and I
> mean loads) of stuff during ejbActivate and ejbPassivate. My whole
> system would crumble if the bean was passivated after each transaction.
> Thank god it is not ;-)

So does this mean your code is not portable or will die a slow death
because other EJB Server vendors have interpreted the EJB specification
differently? Doesn't this mean that the EJB specification should be
changed so that such behaviour can be controlled by us through a
standard API which all vendors support consistently?

Geoff

===========================================================================
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".