CSI attribute management has changed in OpenSAF 4.0 beta3

[karin.holm@…]

Using Appconfig.xml you specified CSI attributes in SI with the following syntax:
<nameValue name="logFile" value="/home/saf-demo/notif.log"/>

This was received in the amfCSISetCallback as:
CSI attribute name = "logFile", value = "/home/saf-demo/notif.log".

With beta 3 release of OpenSAF the CSI attribute is specified as the following IMM object:

<object class="SaAmfCSIAttribute">

<dn>safCsiAttr=logFile,safCsi=ntfSubscribeApp,safSi=SC-NWayActive,safApp=ntfSubscribeApp</dn>
<attr>

<name>saAmfCSIAttriValue</name>
<value>/home/saf-demo/notif.log</value>

</attr>

</object>

and recieved in received in the amfCSISetCallback as:
CSI attribute name = "safCsiAttr=logFile,safCsi=ntfSubscribeApp,safSi=SC-NWayActive,safApp=ntfSubscribeApp", value = "/home/saf-demo/notif.log".

This is quite a change in behavior and makes it hard to code a component independent of the configuration (need to know exactly how it will be configured).

Shall the whole dn for the CSI attribute be used as name in the amfCSISetCallback call?
should not just the name part of the dn for the CSI attribute be used instead?

[kovi@…]

It may be reasonable to discuss this question with the TLC before doing this motion as in an other commercial implementation the full DN is used for the attribute name. Probably the AMF spec is not clear enough in this question.

Anyway this is such a fundamental issue that if it is ambiguous, it needs to be addressed by the Forum as well.

Just my cents.

[marioa]

Lifting up to the TLC to discuss and make decision.
Discussion thread on devel:
http://list.opensaf.org/archives/devel/2009-November/005726.html
http://list.opensaf.org/archives/devel/2009-November/005736.html
/Mario

[marioa]

Based on provided input TLC has decided that behavior must be kept as before (as in OpenSAF Release 3; Basically, only name of attributes returned, not the DN).