I read through this section of the EJB 1.1 spec (Section 14.4 Resource
Manager Connection Factory References). It is not all that clear from
the spec whether a container is required to support connection factories
for resource managers other than JDBC, JMS, and JavaMail. The 3rd party
product I am using conforms to none of those APIs.
The "resource manager connection factory" is a great pattern, but the
problem is that it is a pattern and not an API. The pattern is
implemented
as DataSource for JDBC, something else for JMS, etc.. A container
doesn't
a priori know how to deal with a connection factory. The container must
be coded to deal with DataSource, the JMS connection factory, etc..
So for resource managers that are not JDBC, JMS, or JavaMail, there
seems
to be no standard and portable way to provide a resource manager
connection
factory.
Does the J2EE spec say more about resource managers than the EJB 1.1
spec?
-eric
Assaf Arkin wrote:
>
> > 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
===========================================================================
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".
