Description of the aNtfNotificationReadInitialize() in the NTF-A.01.01 spec is
as below :
-----------------------------------------------------------------------------------
This method is used to initialize reading logged notifications according to the
search
criteria specified by searchCriteria and filters referenced by
notificationFilterHandles.
The search criteria are optional.
-----------------------------------------------------------------------------------
Hence this bug is valid for NTF-A.01.01 spec.
---
** [tickets:#742] search criteria should be made optional for ReadInitialize()**
**Status:** invalid
**Milestone:** future
**Created:** Thu Jan 23, 2014 10:39 AM UTC by Sirisha Alla
**Last Updated:** Tue Jan 28, 2014 11:24 AM UTC
**Owner:** Praveen
Since search criteria for the saNtfNotificationReadInitialize() API is an
optional parameter, the API when called without
any search criteria needs to return SA_AIS_OK. The code as of now is returning
SA_AIS_ERR_INVALID_PARAM which is a bug as per the NTF-A.01.01 specification.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
