> Remy Maucherat wrote: > > > ok. Thanks. I've committed it now, since you seem to think that's a good > idea. > > I've been using it (on our test servers) using the tomcat JNDI context > (in tc4.1-dev), and that seems to work very well
Great ! > (except that, if you > misconfigure something, it swallows the error messages silently > somewhere, I think). Yes indeed, in the JNDI resource factory. If you read tomcat-user, you'll see you're not the only one to have problems here ;-) The thing is there's really nowhere to report any failure because of the nature of JNDI (except on the stderr; maybe it would be better to do that anyway rather than leave users in the dark; or maybe throw a NamingException with some explanation in more cases - I try to avoid doing that as JNDI allows interrogating multiple resource factories as long as they return null). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
