Quoting Ruben DF <[EMAIL PROTECTED]>: > You do not need to download jotm* jars or copy j2ee > jars under the new code. The transaction manager and > j2ee spec jars are provided by Geronimo and are > downloaded by maven when building Kandula. > > The new Kandula_1 code only supports the Geronimo TM > for tx management. > > To get a reference to the TM use Bridge.getTM(); > > Here is where I think is wrong, because those files > should keep at catalina/shared/lib. (In README.1st > says that should keep in that directory, but says
This is correct. I updated the user-guide (the web page). I still need to go through it again. Thanks for pointing it out. > > + for samples/test-suite1 use > "org.apache.kandula.geronimo.TxHandler" in > server-config.wsdd > > + for samples/interopibm use > "org.apache.kandula.coordinator.at.TxHandler" > > It only says about server-config.wsdd file (not > client-config.wsdd). However, if both files, > server-config.wsdd and client-config.wsdd, must have > the same handler, when you downloaded kandula from > svn, why server-config.wsdd has > org.apache.kandula.geronimo.TxHandler and > client-config.wsdd has > org.apache.kandula.coordinator.at.TxHandler?? Those > files should have the same handler by default, > shouldn't they?then, why Test-suite1 works ok having > different handlers in server and client? > > Well, due to client-config.wsdd has always had the > coordinator.at handler for me (I haven't update this > file), the error follow appearing (I have > server-config.wsdd with coordinator.at handler as the > client-config.wsdd) > > What happens? Why have I got that error? The handler used (client or server) depends on the TM. if you want to use a j2ee TM you need to use the o.a.k.geronimo.TxHandler and use Geronimo TM for your tx management. if you are using the o.a.k.coordinator.at."TM" you need to use o.a.k.coordinator.at.TxHandler. Note that this is not a full j2ee TM nor do we intend to develop it towards that end either. It just provides a convenient client interface for those "standalone" applications that just wants to use ws- at. In future ws-at is likely to bridge different tx domains rather than used by itself as demonstrated by the o.a.k.geronimo.Bridge Presently, we do not support exporting j2ee transactions. So the client side handler will always be the latter. However, the server side handler changes on what you intend to do. I think I made a mistake in my previous e-mail when I asked you to deploy geronimo.TxHandler in both files. Sorry about that. --dasarath > > other question: is it necesary to update server.xml > with this code? (test-suite1 works ok without update > that file) (See step3) > > <Context path="/axis" docBase="axis" debug="0" > reloadable="true" crossContext="true"> > <Resource name="jdbc/myDB" auth="Container" > type="javax.sql.DataSource" > factory="org.objectweb.jndi.DataSourceFactory" > username="name" > password="pwsd" > driverClassName="com.mysql.jdbc.Driver" > > url="jdbc:mysql://localhost/axis?useUnicode=true&characterEncoding=UTF-8" > /> > <Resource name="UserTransaction" auth="Container" > type="javax.transaction.UserTransaction" > > factory="org.objectweb.jotm.UserTransactionFactory" > jotm.timeout="60" /> > </Context> > > If i need update that file, where I should put the > code in server.xml , to the end? > > Thanks in advance > Regards > > > > ______________________________________________ > LLama Gratis a cualquier PC del Mundo. > Llamadas a fijos y móviles desde 1 céntimo por minuto. > http://es.voice.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
