Hi Jim,
You can find more info in SAI-AIS-CPROG-B.05.02
On the bottom of page 50, there is an example with associated object.
This is a copy from the spec:
"
For example, considering FIGURE 3, an object of the SaAmfCSIAssignment object
class is a child of an object of the SaAmfCSI object class and has,
accordingly, the
DN format:
"safCSIComp=...,safCsi=...,safSi=...,safApp=...".
The RDN value of the safCSIComp RDN type is set to the DN of the associated
object of the SaAmfComp class. This means that the DN of the object of the
SaAmfCSIAssignment class can be unfolded as:
"safCSIComp=safComp=...\,safSu=...\,safSg=...\,safApp=...,safCsi=...,safSi=...,safApp=...".
Note that the '\' escape character is used within the DN, which is used as an
RDN
value.
"
Thanks,
Zoran
-----Original Message-----
From: Zoran Milinkovic [mailto:[email protected]]
Sent: den 12 september 2017 10:34
To: Carroll, James R <[email protected]>;
[email protected]
Subject: Re: [users] erroneous DN formats?
Hi Jim,
You are talking about associated DN, which means that DN is stored as a value
in RDN.
In your case of
safSISU=safSu=xxx\,safSg=yyy\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF, the
value of safSISU is safSu=xxx,safSg=yyy,safApp=OpenSAF, the value of safSi is
SC-2N, and the value of safApp is OpenSAF.
To be able to store DN as a value in RDN, we escape comma with \
BR,
Zoran
-----Original Message-----
From: Carroll, James R [mailto:[email protected]]
Sent: den 11 september 2017 23:44
To: [email protected]
Subject: [users] erroneous DN formats?
Hi,
I am using OpenSAF 5.2, and have recently discovered the following anomaly.
1) The DN name for Object Class SaAmfSIAssignment, as defined in Section
8.3, Table 21 is defined as
"safSISU=...,safSi=...,safApp=..."
However, the value getting returned by OpenSAF, using the amf-find utility, has
backslashes in the name, and does not follow this naming construct, in some
cases repeating some fields twice. Once example of this is as follows:
safSISU=safSu=xxx\,safSg=yyy\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
2) We have also seen similar erroneous behavior with the DN name for Object
Class SaAmfCSIAssignment, as defined in Section 8.3, Table 21 is defined as
"safCSIComp=...,safCsi=...,safSi=...,safApp=..."
Can you clarify this behavior? It does not appear to meet the standard naming
definitions. In particular, the slashes are causing our software to behave
unexpectedly.
Thanks.
Jim
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech
sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech
sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
