On 2/7/06, Matt Raible <[EMAIL PROTECTED]> wrote: > Howdy all, > > I'm trying to get JOTM working on Tomcat 5.5.x. I'm using 5.5.15 and > I've run into some strange issues. More than anything, I'm looking > for explanations and (hopefully) some help. > > I've updated the following tutorial for Tomcat 5.5.x: > > http://jotm.objectweb.org/current/jotm/doc/howto-tomcat-jotm.html > > My update: http://static.raibledesigns.com/downloads/howto-tomcat-jotm.html
> To summarize: > > Why can't a UserTransaction resource be in context.xml with Tomcat 5.5.x? > Why can't a factory attribute be specified on a datasource with Tomcat 5.5.x? > > Both of these settings work fine on Tomcat 5.0.28. I'm on OS X with JDK 5. > > Of course, if anyone knows of a easier transaction manager to > integrate into Tomcat, I'm all ears. ;0) The main thing I don't understand is how that jndi implementation manages to take over the enc without any configuration. IMO, since it's there and you have to disable it explicitely anyway with special config, the best thing (assuming it works) is to configure their JNDI rather than using Tomcat's JNDI. For 1), it's simple: Resources are bound in "comp/env", while the UserTransaction should go in "comp". ResourceLink has a special case for UserTransaction, so it works. There's a special Transaction element which would avoid having to do that, but it's not implemented. It wouldn't be hard to add support for it in org.apache.catalina.core.NamingContextListener. For 2), it seems to work for me in all cases (the factory attribute is never ignored, although classloading may fail). This is unrelated, but your context.xml is wrong, and should not include "path="/dbtest" docBase="dbtest.war" debug="0"". -- xxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
