Issue 2666:  Clarify specification text in section 3.4 Log Generated Events                                                                                                                                         (log_service-ftf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: The specification text is unclear and should make a note in 
 section "3.4 Log Generated Events" to explain that the manner
 in which logs send log generated events to their corresponding 
 log factories is an implementation detail. 
 
 The idea is that applications (log/LogFactory clients) are only consumers
 of log emitted events, they do not send events to the factory. Therefore, the 
 LogFactory does not need to expose the SupplierAdmin interface. How the log
 actually forwards events to the factory is left up to the implementation -
 use a SupplierAdmin object, or other means.
 
 

Resolution: resolved, see revised text below
Revised Text: Resolution: 
The idea is that applications (log/LogFactory clients) are only consumers of log 
emitted events, they do not send events to the factory. Therefore, the LogFactory 
does not need to expose the SupplierAdmin interface. How the log actually forwards 
events to the factory is left up to the implementation - use a SupplierAdmin object, 
or other means. 

Revised Text: 
Specification Text 
Section 3.4: Log Generated Events 
NOTE: Log factories are responsible for the creation, deleation, management of logs, 
as well as a supplier of events. A Log factory is not intended to be a consumer of events 
and therefore does not expose a SupplierAdmin interface. It is left up to an implementation 
detail as to how log generated events are passed from a log to it's log factory. 

Specifcation IDL 
No changes 

Actions taken: 
Completed.
Actions taken:
May 27, 1999: received issue
July 27, 1999: closed issue
Discussion: 

End of Annotations:=====
Sender: spruce@ovdm40.cnd.hp.com
Message-ID: <374B4B01.94936F4B@fc.hp.com>
Date: Tue, 25 May 1999 19:14:41 -0600
From: Stephen Spruce <spruce@fc.hp.com>
Organization: Telecom Management Division
X-Mailer: Mozilla 4.08 [en] (X11; I; HP-UX B.10.20 9000/777)
MIME-Version: 1.0
To: juergen@omg.org
Subject: Issues for Telecom Log Service
Content-Type: multipart/mixed;
boundary="------------5359345BE554D3D338D5D19C"
X-UIDL: 30aaae3f45cba14fe2a8031cca11ac75

Hi Juergen,

Attached is a list of issues that have been brought up against 
the Telecom Log Service (TLS) since it reached the Adopted
Specification
stage. I am not exactly clear on the content that is necessary 
for these issues, so let me know if you need more information 
about any or all of them. 



ISSUE
-----
(from Keith Hyland: Keith.Hyland@wcs.eraj.ericsson.se)

The specification text is unclear and should make a note in 
section "3.4 Log Generated Events" to explain that the manner
in which logs send log generated events to their corresponding 
log factories is an implementation detail. 

The idea is that applications (log/LogFactory clients) are only
consumers
of log emitted events, they do not send events to the
factory. Therefore, the 
LogFactory does not need to expose the SupplierAdmin interface. How
the log
actually forwards events to the factory is left up to the
implementation -
use a SupplierAdmin object, or other means.