Is the order that Tomcat 6.0.x loads/instantiates Custom Resources
definable? If so, how? If not, is there a way to ensure that one custom
resource is loaded prior to another one?
Tomcat 4.x seemed to have the behavior that custom resources were created in
the order they appear in the server.xml file. I'm migrating an application
that appears to have a dependency on that order of loading. It runs fine in
Tomcat 4.0 (and Sun Web server 6.x), but it's failing to load in Tomcat 6.0.
It throws an error where one custom resource object refers to another that's
available via JNDI but that item hasn't been loaded yet.
Dave
