Hi All, First of all I'd like to note that I've found mailing in the archives about this subject and it's foreign to my nature to repeat already mentioned things, but I'd like to clarify additional things.
I 'd really appreciate if somebedy could help out me in the following things ;) Additional space character(s) after attribute value destroy(s) the whole attribute value, it seems it is displayed as a binary value or it's the standard behaviour due to the line64 coding or it's a bug? Please look at the following example: 1.The subtree has exported with JX 3.1 the appNames="Hello" version: 1 dn: administratorId=0,applicationName=platform,nodeName=jambala objectClass: JIM-Administrator administratorId: 0 administratorName: jambala appNames: Hello attributes: toolbox.all=true defaultPermissions: 9 failedCount: 0 groupId: 0 groups: 0:0 isAnonymous: TRUE maxSeconds: 1200 ownerId: 0 permissions: 9 shareTree: nodeName=jambala 2.The subtree has exported with JX 3.1 the appNames="Hello " (+1 space) version: 1 dn: administratorId=0,applicationName=platform,nodeName=jambala objectClass: JIM-Administrator administratorId: 0 administratorName: jambala appNames:: SGVsbG8g attributes: toolbox.all=true defaultPermissions: 9 failedCount: 0 groupId: 0 groups: 0:0 isAnonymous: TRUE maxSeconds: 1200 ownerId: 0 permissions: 9 shareTree: nodeName=jambala 3.Listing the same subtree with ldapsearch command of Openldap server, the ldif dump is the same: #ethths mwlx102> ldapsearch -x -h 172.31.61.24 -p 7323 -b "administratorId=0,applicationName=platform,nodeName=jambala" -D "administratorName=jambala,nodeName=jambala" -w pokemon # extended LDIF # # LDAPv3 # filter: (objectclass=*) # requesting: ALL # # 0, platform, jambala dn: administratorId=0,applicationName=platform,nodeName=jambala objectClass: JIM-Administrator ownerId: 0 groupId: 0 shareTree: nodeName=jambala permissions: 9 administratorId: 0 administratorName: jambala groups: 0:0 defaultPermissions: 9 maxSeconds: 1200 attributes: toolbox.all=true failedCount: 0 isAnonymous: TRUE appNames:: SGVsbG8g # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 #ethths mwlx102> 4. Repeating the same ldapsearch with -t parameter (meaning: write binary values to files in temporary directory) and using cat command to get the readable value: #ethths mwlx102> ldapsearch -x -h 172.31.61.24 -p 7323 -b "administratorId=0,applicationName=platform,nodeName=jambala" -D "administratorName=jambala,nodeName=jambala" -w pokemon -t # extended LDIF # # LDAPv3 # filter: (objectclass=*) # requesting: ALL # # 0, platform, jambala dn: administratorId=0,applicationName=platform,nodeName=jambala objectClass: JIM-Administrator ownerId: 0 groupId: 0 shareTree: nodeName=jambala permissions: 9 administratorId: 0 administratorName: jambala groups: 0:0 defaultPermissions: 9 maxSeconds: 1200 attributes: toolbox.all=true failedCount: 0 isAnonymous: TRUE appNames:< file:///tmp/ldapsearch-appNames-rrYSI3 # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 #ethths mwlx102> cat /tmp/ldapsearch-appNames-rrYSI3 Hello #ethths mwlx102> My question would be it's the standard behaviour or it's a bug in Jx and ldapsearch? If it's the standard working, somebody could send the related RFC number (possibly number of chapter ;) to me? Thank Your for the help and cooperation! Regards, /Sandor ( from ///ericsson ) ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Jxplorer-devel mailing list Jxplorer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jxplorer-devel
