Actually ResourceFactory, which would potentially enlist a resource in a
transaction if it supports XAResource and potentially pool a resource if
it supports a pooling interface.
I've started looking at the problem a while ago and have come up with an
API for that. It's part of the Tyrex open source project
(http://tyrex.exolab.org).
If you have CVS access, you can get these sources from the CVS (they are
experimental so they're only available from the CVS). If not I can send
them to you in a separate e-mail.
arkin
Frank Sauer wrote:
>
> Do you think it is possible to come up with a standardized
> interface called ResourceManager that defines what it means
> to be managed? That way we could add our own and get rid of
> all these restrictions.
>
> Frank
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Assaf Arkin
> > Sent: Tuesday, February 22, 2000 1:04 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Amended list of resource managers (was: Re:
> > Threadsquestion)
> >
> >
> > I don't remember the formal definition, but a resource is
> > anything that
> > your application might wish to use, has a cost, and as such must be
> > managed. The resource manager is actually not part of the EJB server.
> > The RDBMS, LDAP server, SMTP agent are resource managers.
> >
> > The EJB container (more specifically the transaction manager) manages
> > pooling, transaction enlistment, security, and quotas on all these
> > resources based on a policy that best fits the application.
> >
> > All resources are exposed through the JNDI environment naming context.
> >
> > JDBC, JMS, URL and JavaMail are on that list for EJB, JDBC
> > and JMS also
> > include the necessary APIs for pooling and transaction enlistment.
> >
> > arkin
> >
> >
> > Laird Nelson wrote:
> > >
> > > "John K. Peterson" wrote:
> > > > > 1. JNDI
> > > > > 2. JDBC
> > > > > 3. JMS
> > > > Don't forget (for J2EE):
> > > > 4. URL
> > > > 5. JavaMail
> > >
> > > OK. So do the previous 5 items constitute the official
> > list of resource
> > > managers for the 1.1 specification? Sun? Anyone out there? Does
> > > anyone know why they are resource managers? What are they managing?
> > > What is a resource? How were the five items listed determined to be
> > > resource managers? Is there documentation (I'll go check the spec.)
> > > other than the spec. that lists these somewhere?
> > >
> > > Cheers,
> > > Laird
> > >
> > >
> > ==============================================================
> > =============
> > > 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".
> >
> >
>
> ===========================================================================
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
