> I am looking at a 3rd party product that keeps a shared object cache in
> memory. The cache is read and updated by many beans concurrently.
Your 3rd party product constitues a resource manager. It should conform
to the J2EE model whereby a resource manager is accessed through the
JNDI environment naming context, is subject to the server's transaction
processing management, is aware of all the reliability/consistency
issues, etc.
This is precisely how EJB deals with JDBC drivers, JMS messaging, and
ERP connectors, all of which are 3rd party code that is not part of the
EJB server or the Java runtime.
arkin
>
> I am trying to find out whether this is "portable" or not. From my
> understanding of the EJB 1.1 specification, this is not guaranteed to be
> portable between EJB servers. The vendor thinks that it is portable
> because their code is not part of the bean. But I remain unconvinced
> that
> the EJB restrictions do not apply to their code as well.
>
> If anyone can provide clarification on this issue, it would be
> appreciated.
>
> Thanks,
>
> -eric
>
> ===========================================================================
> 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".
