Hi!
> ||Thanks Aaron for pointing this out.
> |I still do nut fully understand the implications of not having any
> |transactions on the database level. As long as just one application
>
> Actually the decision to commit the data is done at teh app layer by the
app
> server with or without enrolment of the connection in the transaction. So
> yes the "not having the db" participating is not a 'show stopper', just
that
> if the db goes down during a write you are screwed.
Depends. If the decision that the data is invalid is done in ejbStore then
you're screwed since other entities might have been ejbStored allready and
cannot be rolled back in the DB.
> |server uses the database I can't see how data could get corrupted. I
> |thought the application server guarantees to have synchonized business
> |method calls. And after each call the data is stored back into the
> |database. Where does the corruption come in ?
>
> No corruption I agree. The corruption is only if the "write" goes bad,
but
> the application Tx is only in EJB layer.
As above, store might do more than just store.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
