Actually that's not quite true. Some vendors will allow new transactional
resources to plug into the EJB transaction framework.
<vendor>
GemStone/J allows this through the CORBA transaction service...
We provide off the shelf tx resources for JDBC a GemStone/J's
cache....
</vendor>
> -----Original Message-----
> From: Chip Wilson [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 19, 1999 4:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: BMP(non-database) & transaction behaviour
>
> You can only use a persistent store that is supported by your EJB
> container,
> even if you are doing Bean-Managed Persistence. If you want to store
> beans
> in flat files, then you will need a flat file database that is supported
> by
> your container, for exactly the reason that you describe -- the
> transactions
> must be integrated. BMP does not allow you to use any arbitrary
> persistent
> store with any ejb container.
>
> > -----Original Message-----
> > From: Juliano Junio Viana [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, May 20, 1999 2:34 PM
> > To: [EMAIL PROTECTED]
> > Subject: BMP(non-database) & transaction behaviour
> >
> > Hi,
> >
> > I am pretty new to ejb, but i think this issue was not adressed on this
> > list before ( if it is a issue at all :) )
> > I have some BMP entity ejb�s that do *not* store information on
> > JDBC-aware databases.
> > One such creature is a ejb that represents a virtual domain. The virtual
> > domain�s configuration is stored in a configuration file used by the
> > web server, and the ejb parses the file on ejbLoad() and changes the
> > file on ejbStore().
> > I have found a problem with this approach: the entity beans are never
> > notified of a tranaction rollback. So, if i have method calls on several
> > beans in the same transaction, when i commit the transaction my bean
> > will receive a ejbStore() call, but if the transaction is rolled back it
> > will never know ( and therefore never be able to roll back the change).
> > In the spec�s sequence diagrams, the rollback notification goes to the
> > database(as a resource registered with the transaction coordinator ),
> > but in this case there is no " database" .
> > Any sugestions on how can i make my ejb transaction aware in this case?
> >
> > Regards,
> >
> > Juliano.
> >
> >
> ==========================================================================
> > =
> > 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".
