Issue 2665:  Argument in CapacityAlarmTresholdList tresholds doesn"t appear in IDL                                                                                                                                  (log_service-ftf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: In the specification text, the BasicLogFactory::create() and 
 BasicLogFactory::create_with_id() operations have an extra
 argument, in CapacityAlarmThresholdList thresholds, which does
 not appear in the specification IDL. The reference to thresholds
 in the specification text should be removed from the definitions
 of BasicLogFactory::create() and BasicLogFactory::create_with_id().
 
 The paragraphs in the specification text that describe the create()
 and create_with_id() operations for the other log factories
 (ie. EventLogFactory) should explain that they have an additional
 argument, thresholds, besides the ones defined in the BasicLogFactory.
 

Resolution: resolved, see revised text
Revised Text: Resolution: 
BasicLogs do not have a notion of thresholds and therefore the text needs to be changed. 
The reference to thresholds in the specification text should be removed from the definitions 
of BasicLogFactory::create() and BasicLogFactory::create_with_id(). The paragraphs in 
the specification text that describe the create() and create_with_id() operations for 
the other log factories should explain that they have an additional arguments and raise 
addition exceptions besides the ones defined in the BasicLogFactory. 

Revised Text: 
Specification Text 
Section 3.3.3: Log Creation 
    BasicLog create ( 
        in LogFullActionType full_action, 
        in unsigned long max_size, 
        out LogId id 
    ) raises (InvalidLogFullAction); 

    The create() operation in the BasicLogFactory interface allows clients to create new BasicLog objects. 
    The log full action and maximum size must be specified at creation time, but can be changed later. 
    The log id will be generated and returned as an out parameter. Exceptions are as follows: 

     An InvalidLogFullAction exception is raised if the full_action specified is not valid. 

    The create() operation in the EventLogFactory, NotifyLogFactory, TypedEventLogFactory and 
    TypedNotifyLogFactory interfaces creates new BasicLog, NotifyLog, TypedEventLog, and 
    TypedNotifyLog objects respectively. Each create() operation for the log factories takes arguments 
    and raises exceptions that are appropriate for the type of log being created. 

    BasicLog create_with_id ( 
        in LogId id, 
        in LogFullActionType full_action, 
        in unsigned long max_size 
     ) raises (LogIdAlreadyExists, InvalidLogFullAction); 

    The create_with_id() operation in the BasicLogFactory interface allows clients to create new BasicLog 
    objects specifying the id to be used. The log full action and maximum size must be specified at creation time, 
    but can be changed later. The log id is specified as an in parameter. Exceptions are as follows: 

     A LogIdAlreadyExists exception will be raised if this log id exists within the scope of the log factory. 
     An InvalidLogFullAction exception is raised if the full_action specified is not valid. 

    The create_with_id() operation in the EventLogFactory, NotifyLogFactory, TypedEventLogFactory, 
    and TypedNotifyLogFactory interfaces create new EventLog, NotifyLog, TypedEventLog, and 
    TypedNotifyLog objects respectively. Each create_with_id() operation for the log factories takes 
    arguments and raises exceptions that are appropriate for the type of log being created. 

Specification IDL 
Modify BasicLogFactory to raise correct exceptions: 

module DsLogAdmin { 
    ... 
    interface BasicLogFactory : LogMgr { 
        BasicLog create ( 
            in LogFullActionType full_action, 
            in unsigned long long max_size, 
            out LogId id 
        ) raises (InvalidLogFullAction); 

        BasicLog create_with_id ( 
            in LogId id, 
            in LogFullActionType full_action, 
            in unsigned long long max_size, 
        ) raises (LogIdAlreadyExists, InvalidLogFullAction); 
    }; 
}; 

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 


ISSUE
----- 
(from Dimitris Andreadis: andd@intracom.gr)

In the specification text, the BasicLogFactory::create() and 
BasicLogFactory::create_with_id() operations have an extra
argument, in CapacityAlarmThresholdList thresholds, which does
not appear in the specification IDL. The reference to thresholds
in the specification text should be removed from the definitions
of BasicLogFactory::create() and BasicLogFactory::create_with_id().

The paragraphs in the specification text that describe the create()
and create_with_id() operations for the other log factories
(ie. EventLogFactory) should explain that they have an additional
argument, thresholds, besides the ones defined in the BasicLogFactory.