Quoting Dominik Heller <[EMAIL PROTECTED]>: The TestSuite1 contains examples of both.
If you are using a J2EE container then Kandula should be passed a reference to the transaction manager of that container. So when your application receives a web service request, Kandula can convert the incoming coordination context to a suitable JTA transaction and attach that tx to the thread executing your application logic. So that the method invocation will be performed under a transaction context-- J2EE in this case. Kandula will later on terminate this transaction when the coordination context is terminated. In the source you get from SVN, the Bridge class simply creates its own instance of J2EE transaction manager. This is not correct as it would create two separate TM instances inside the same J2EE container. At this point the details are very much container specific. We also have to consider how much isolation there exists between different J2EE containers e.g. Servelet container and EJB container. This work was motivated by JSR109 long ago. -- Dasarath > Hey Dasarath, > I have developed my Application pretty close to the Banking example, so I am > using the TransactionManagerImpl on the clientside and a transactionManager > which is bridged from geronimo. So right now I have a non-J2EE application, > if I would want to create a J2EE app, I could use the geronimo > transactionManager directly, right? Which are the two TxHandlers can you > point me to them and to the sample code for both approaches? > > THX > -Dominik > > > -------- Original-Nachricht -------- > > Datum: Wed, 30 Jan 2008 10:08:12 -0500 > > Von: Dasarath Weeratunge <[EMAIL PROTECTED]> > > An: Dominik Heller <[EMAIL PROTECTED]> > > CC: [email protected] > > Betreff: Re: Kandula 1 > > > 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 > > > > > > > -- > GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. > Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
