Why does Xerces do 'exit(-1)' if it can't find the message domain? Shouldn't it just throw a hardcoded "I can't find my message file!" error, which will be sent to the ErrorHandler. That would allow calling applications to handling and log the error appropriate.
It seems terrible to me, as someone using Xerces in production code, that in the case of a missing env var (XERCES_NLS_HOME), a background process may quietly die without logging anything. I must be missing the justification. dan ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
