In the JAxMeXS object model (most org.apache.ws.jaxme.xs.* interfaces), no traversal methods besides XSType.getSimpleType() and .getComplexType() throw SAXException. However, those two methods do.
Is that intentional? It seems like an irregularity that should eventually be fixed.
(Consider writing a group of methods to traverse a schema. Most of your code, calling other JaxMeXS object-model methods, does not need to handle SAXException. However, when you process a type and call method getSimpleType() and getComplexType(), all of the sudden you have to handle SAXException. This seems strangely inconsistent.)
Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
