Microsoft's suite of middleware technologies is introducing the concept of a compensating resource managers (if COM+ ever ships). Basically, you create a component that implements a couple of interfaces. One interface is used to integrate with OLE Transactions (the equivalent of JTS) and vote on the outcome of transactions. The other interface is used to allow notification of the outcome of a transaction (including a durable log). That allows the non transactional resource to issue a compensating action for any rolled back transaction.
Does anyone who is following the EJB standards process know if we are going to get functionality like this any time soon. It sounds like the connector architecture is a first step and would provide a convenient place to house such functionality.
Erik
--
Erik Huddleston, [EMAIL PROTECTED]
Chief Architect, eCustomers.com
Microsoft Java MVP
> -----Original Message-----
> From: Kirk Pepperdine [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 10, 1999 6:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: BMP with LDAP
>
>
> >Confirmed. You can get an LDAP JNDI SPI from either JavaSoft (look in
> >the JNDI page) or Netscape (the Mozilla Directory SDK).
> >
> >That still does not make LDAP transactional, but I don't see why you
> >couldn't use LDAP for persistance. After all if you are
> updating LDAP,
> >whether through the LDAP API, JNDI or BMP you get the same
> >non-transactional persistance.
>
> [Kirk] What happens when the LDAP is involved in a
> distributed transaction
> that gets rolled back?
>
> >
> >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".
>
