Processing extra config XML in servlet init relayed on DTD/SXD in app context

[D Rog]

I have a servlet which reads extra configuration files in init method. It uses getResource or something like that to obtain the files. These files have references to DTD/XSD inside of a context of the web application. If the servlet has delayed availability, then config files get processed fine. However if it has an init at load, then references can't be found and parsing of extra config get failed. This behavior is web container dependent. Can somebody recommend more robust solution to get consistent behavior on any web container regardless of order of servlet initialization.

[Rahul Bhattacharjee]

Do you have any configuration property file for you application.If yes then you can set property for resolution.
Now you can use something like DTD entity resolver (EntityResolver interface)to resolve the DTD location , which in turn would read the property to find the exact location.This is way your appplication becomes independent of application startup.