Graham, when checking your WODEN-14 patch prior to committing it I noticed some resolver code that catches checked exceptions and rethrows them wrapped as RuntimeException. Obviously you have to conform to the interfaces you implement (e.g. URIResolver) so can't just declare new checked exceptions on the methods.
However, as the code stands these exceptions will surface as RuntimeException to the Woden client without any further reporting or error handling by Woden. Perhaps Woden should detect these and do some sort of reporting or error handling - perhaps using the Woden ErrorReporter within the resolver code to report the errors before rethrowing or perhaps adding a RuntimeException catch block in the Woden code at the points where XmlSchema might use our resolver (e.g. parseSchemaImport) and checking if any caught RuntimeException contains a wrapped checked exception that we need to report or rethrow as a WSDLException. Not urgent, but maybe we can discuss further after the Interop next week. regards, John Kaputin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
