Hi everyoneI Primary Address book ODS 41 server version 5.0.9a and secondry Address book ODS 41 and versio 5.0.6a. A java application in websphare server using JNDI create the XML and put this XML in Secondry address book in a text field.
Now there is another apps ODS 20 server version 4.6.7 which has a agent, which run by a user manually with proper access to run the agent and copy the XML file from secondry address book field to Primary address book same name field, but when agent copy the XML file from secondry to primary field, and user tried to open the XML file in web browser, error come up.
Is it different server and notes version make that error. please let me know.
Thanks
Subject: Does different ODS and server version can cause the problem when runing agent …
are you saying that if you open this same field in the same browser on 5.0.9a it works and on 5.0.6a it doesn’t?
Stan is right about the extra character – it is most probably 0xD. Notes does not allow store single 0xA or LF in a text field using LS. It always adds 0xD (CR) also. That’s the explanation why you have this extra char after copying the field content using LS. The only to way AFAIK to copy over plain 0xA is by using C API, but that should not matter in this case.
So the answer could be in content-type header. Is it text/xml in both cases; or?
Subject: RE: Does different ODS and server version can cause the problem when runing agent …
HiIf I manually copy and past the XML blob from secondry address book to primary address book then it work fine but the following it didn’t work.
If priUser.HasItem(“BranchProfile”) Then Call priUser.RemoveItem(“BranchProfile”)
End If
Call secXML.CopyItemToDocument(PriUser, “BranchProfile”)
'save synced XML BLOB (beware of the Blob) Call priUser.Save(True, True)
and by theway what is LF is.
do you know how which method should I use so it will same as manually copy and past field content.
and how can I get C API to fix the extra character.
Thanks for help
Lisa
Subject: RE: Does different ODS and server version can cause the problem when runing agent …
“it works fine” refers to display in browser or to the fact that you manage to enter the text without extra character? Or both?
LF is linefeed or Chr(10) or 0xA; thing about C API was to use C API to copy item instead of LS, say NSFItemCopy. Still it’s hard to understand how carriage return (char 13) could cause problems.
Using of C API may not be outright simple without some experience, so it would be better to find some other culprit than this extra character that IMO is a legal whitspace character in XML. Did you check the content-header?
Subject: Does different ODS and server version can cause the problem when runing agent …
ODS won’t cause the problem, but MIME type will – even if the text in the file is in perfect condition and is completely valid, the browser may reject the file if it is not of the correct MIME type.
Subject: RE: Does different ODS and server version can cause the problem when runing agent …
Hi How I can fix the MIME type problem and how I know that text is correct MIME type.
Thanks for always quick help.
Lisa
Subject: RE: Does different ODS and server version can cause the problem when runing agent …
"When I view the document in document properties it showing me some kind of pipe ( thicker then pipe)
i.e
Following XML in a field
<Transit>54528</Transit>
<RoleType>EXC</RoleType>
<RoleLevel>4</RoleLevel>
<Telephone>416811111</Telephone>
and in document properties it look like this
Field Name: BranchProfile
Data Type: Text List
Data Length: 210 bytes
Seq Num: 2
Dup Item ID: 0
Field Flags: SUMMARY
"
|| ( when view in doc properties thick pipe)
|
<Transit>54528</Transit>|
<RoleType>EXC</RoleType>|
<RoleLevel>4</RoleLevel>|
<Telephone>4168621111</Telephone>|
|
|
"
any idea
Lisa
Subject: RE: Does different ODS and server version can cause the problem when runing agent …
That’s just the carriage returns. There is no problem with the data, the problem is that the server is not telling the browser what TYPE of data it is. I’m afraid I don’t know enough about R4.x to help you with that, but I can tell you to stop looking at the XML.