Carolyn Beeton wrote: > The strings would have a format "<type>: msg" such as: > version.mismatch: software '3.11.8' != config '3.11.7' I like this format. Then, in the sipXconfig localized message bundle, we would have localized labels for "version.mismatch" alongside the message.
> stderr.msg-18: java.io.FileNotFoundException: /sipxconfig-logins.log > (Permission denied) > stderr.msg-19: at java.io.FileOutputStream.openAppend(Native Method) I don't know if I like showing the Java exception class name - others may disagree here - maybe at least we should map the exception name/message to a more user friendly message. > (I have limited the maximum number of messages to 100, as some processes > might be very wordy. To show this, I have added an index number. What > do people think about a limit?) A limit is good, I think - but is it possible to have a way to indicate that the list of errors was truncated? Possibly even to have a way to retrieve the additional errors if desired? Or do you think this is not necessary? > The idea is that the Status field on the Servers/Services page could be > clickable, and would display these messages. This is exactly what I had in mind. > Please let me know if this sounds like a good direction to proceed in. From my perspective, as a consumer of this information, I love it. Joe _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
