After an hour or so of debugging, I've reached the conclusion that this is
more trouble that it is worth to me.
The problem is that the naming resources are setup in the middle of the
START process. So, there's no very good way to arrange for some code to run
after the JNDI structure is in place,
2013/4/1 Benson Margulies :
> When embedding Tomcat, I'd like to create some objects purely from code --
> I don't want to bother to express them as XML -- and then pick them up
> inside webapps. Now, calling enableNaming() on Tomcat sets up a bunch of
> environment, but does not actually create a
When embedding Tomcat, I'd like to create some objects purely from code --
I don't want to bother to express them as XML -- and then pick them up
inside webapps. Now, calling enableNaming() on Tomcat sets up a bunch of
environment, but does not actually create and JNDI objects. If I call
enableNam
