> By this token, JNDI and JavaMail are not Resource Managers by any
> stretch of the imagination. Neither promises atomicity or isolation.
> You can't start a transaction, do two binds into a JNDI tree, and
> commit the transaction. There is no requirement on JNDI to provide the
> guarantee that either both binds succeed or neither succeeds. I
> don't understand what URL is doing in this list above.
I agree that the terms used here were confused. JavaMail and URL are
actually resource factories, not resource managers. They can be used to
obtain a connection or a service, although not a transactional one.
JDBC and JMS are also resource factories, while the database server
itself or the messaging middleware are the resource managers.
JNDI is an environment feature, neither a specified resource factory
(why?) nor a resource manager (no transactions).
arkin
>
> So far, the only resource managers I am aware of have come in the form
> of databases, transactional queuing systems, and transactional file
> systems. (Incidentally, NTFS claims to be a transactional file system.
> That is misleading. It is transactional only for file meta data, not
> for your data)
>
> Hope this was the answer you were looking for.
>
> -Sriram
>
> (Principal Engineer, BEA/Weblogic)
>
> ===========================================================================
> 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".
