Description David McCann 2011-06-23 12:07:56 EDT

We currently do not handle validation and errors very well in the runtime portion of DBWS.  Bug 340723 is a good example of this.  In that case, an invalid log level in the sessions.xml file caused the application not to load, but the exception did not indicate the actual cause.  We resolved the builder-side of the equation for that particular issue by checking the log level, and if invalid we log a warning and set a valid default value.  This cannot be done easily in the runtime code, as the exception gets swallowed up by core code, and even if we have access to it we don't currently have any way to log the warning on the server.