Issue 8829: Section: 1.2.5.1 (log-service-rtf) Source: (, ) Nature: Clarification Severity: Critical Summary: I am in the process of updating TAO's Logging Service implementation. Section 1.2.5.1 stats "The Telecom Log Service proposes to define the following OMG Standard exception codes for use with the CosEvent and CosNotification push operations..." and goes on to mention a LOGFULL and LOGOFFDUTY minor code for the NO_RESOURCE [sic] SystemException, a LOGLOCKED minor code for the NO_PERMISSIONS SystemException, and a LOGDISABLED minor code for the TRANSIENT SystemException. TAO does not define these minor codes, so I checked the latest CORBA spec (3.0.3 / formal/04-03-12) and they are not in Appendix A either. What exactly does the spec mean "proposes to define" and what should an implementer do to handle these errors in the here and now. Resolution: Revised Text: Actions taken: May 31, 2005: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 May 2005 02:07:25 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: J.T. Conklin Company: Identity Engines mailFrom: jtc@idengines.com Notification: Yes Specification: Telecom Log Service Specification Section: 1.2.5.1 FormalNumber: formal/03-07-01 Version: 1.1.2 RevisionDate: 07/01/2003 Page: 1-19 Nature: Clarification Severity: Critical HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Description I am in the process of updating TAO's Logging Service implementation. Section 1.2.5.1 stats "The Telecom Log Service proposes to define the following OMG Standard exception codes for use with the CosEvent and CosNotification push operations..." and goes on to mention a LOGFULL and LOGOFFDUTY minor code for the NO_RESOURCE [sic] SystemException, a LOGLOCKED minor code for the NO_PERMISSIONS SystemException, and a LOGDISABLED minor code for the TRANSIENT SystemException. TAO does not define these minor codes, so I checked the latest CORBA spec (3.0.3 / formal/04-03-12) and they are not in Appendix A either. What exactly does the spec mean "proposes to define" and what should an implementer do to handle these errors in the here and now.