Quoting Dominik Heller <[EMAIL PROTECTED]>: Geronimo handles J2EE transactions. If your application uses any J2EE artifacts, any transactions that involve them are handled by Geronimo (or its equivalent). Now, if you write web service whose implementation is in J2EE (e.g. an EJB or Servelet), Kandula forwards incoming web services transactions on to J2EE transaction infrastructure (e.g. J2EE). In effect, your J2EE domain becomes a branch of the web services transaction.
In the unlikely case that your application does not use J2EE but uses resources directly, Kandula has a minimal transaction manager similar to Geronimo that can handle XAResource interface. We have sample code that illustrate both approaches. The latter is just for experimentation. This is also why we have two TxHandlers. -- Dasarath > Hey Dasarath, > I have a question regarding Geronimo. Is the Geronimo used by Kandula the > transaction core for all the transactions? I allready know that Geronimo > provides a transaction API similar to JTA, but is Geronimo the engine in the > background or what exactly is the purpose of its existence. > > THX > > Dominik > -- > Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
