11
XML / Re: XML SortByTag
« Last post by Chilkat on June 04, 2018, 04:54:37 PM »Worked fine for me in v9.5.0.73
News:
Recent Posts
12
XML / XML SortByTag
« Last post by gertir on June 04, 2018, 08:34:33 AM »Hi,
I'm trying to sort all nodes by name, but I'm getting unexpected behaviour.
What I expect is then mod:clausule nodes would be ordered right after mod:afsluitprovisieproducent.
Howeverthese nodes are ordered at the beginning, before mod:aantalstappenafbouwregeling.
When I remove one (random) mod:clausule node, all other mod:clausule nodes are sorted like expected.
Chilkat version is 9.5.0.54.
Here's the xml:
<?xml version="1.0" encoding="utf-8" ?>
<mod:subpolis pc="W">
<mod:aantalstappenafbouwregeling>0</mod:aantalstappenafbouwregeling>
<mod:afsluitprovisie>0</mod:afsluitprovisie>
<mod:afsluitprovisieperc>0</mod:afsluitprovisieperc>
<mod:afsluitprovisiepercproducent>0</mod:afsluitprovisiepercproducent>
<mod:afsluitprovisieperctp>0</mod:afsluitprovisieperctp>
<mod:afsluitprovisieproducent>0</mod:afsluitprovisieproducent>
<mod:omsproductcode>Uitgebreide gevarenverzekering</mod:omsproductcode>
<mod:omssoortverzekering>Brand</mod:omssoortverzekering>
<mod:pakketkorting>0</mod:pakketkorting>
<mod:prolongatiepremieperjaar>255.56</mod:prolongatiepremieperjaar>
<mod:prolpremieexclpakketkorting>63.89</mod:prolpremieexclpakketkorting>
<mod:promillagedooreen>1.28</mod:promillagedooreen>
<mod:soortpolis>0</mod:soortpolis>
<mod:soortverzekering>BR</mod:soortverzekering>
<mod:tekencommissie>7.39</mod:tekencommissie>
<mod:tekencommissieperc>0</mod:tekencommissieperc>
<mod:tekencommissieperctp>0</mod:tekencommissieperctp>
<mod:tekencommissietp>0</mod:tekencommissietp>
<mod:toekomstprovisie>0</mod:toekomstprovisie>
<mod:transactiecode>0</mod:transactiecode>
<mod:transactiestatus>In behandeling</mod:transactiestatus>
<mod:verzekerdbedrag>165000</mod:verzekerdbedrag>
<mod:vrijveld10>0</mod:vrijveld10>
<mod:vrijveld13>0</mod:vrijveld13>
<mod:vrijveld14>0</mod:vrijveld14>
<mod:vrijveld6>0</mod:vrijveld6>
<mod:vrijveld7>0</mod:vrijveld7>
<mod:vrijveld8>0</mod:vrijveld8>
<mod:vrijveld9>0</mod:vrijveld9>
<mod:clausule pc="W">
<mod:internclausulenummer>1</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>504</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>505</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>512</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>692</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>692</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>1311</mod:internclausulenummer>
</mod:clausule>
<mod:conditie pc="W">
<mod:internconditienummer>187</mod:internconditienummer>
</mod:conditie>
<mod:mijverdelingpolis pc="W">
<mod:maatschappijnummer>VN013</mod:maatschappijnummer>
</mod:mijverdelingpolis>
<mod:polisvrij pc="W">
<mod:revisienummer>0</mod:revisienummer>
<mod:rubriek1>Royement i.v.m. opzegging</mod:rubriek1>
</mod:polisvrij>
<mod:tekstpolis pc="W">
<mod:bloknummer>1</mod:bloknummer>
<mod:paginanummer>1</mod:paginanummer>
<mod:revisienummer>0</mod:revisienummer>
</mod:tekstpolis>
<mod:acceptatiepunten>0</mod:acceptatiepunten>
</mod:subpolis>
I'm trying to sort all nodes by name, but I'm getting unexpected behaviour.
What I expect is then mod:clausule nodes would be ordered right after mod:afsluitprovisieproducent.
Howeverthese nodes are ordered at the beginning, before mod:aantalstappenafbouwregeling.
When I remove one (random) mod:clausule node, all other mod:clausule nodes are sorted like expected.
Chilkat version is 9.5.0.54.
Here's the xml:
<?xml version="1.0" encoding="utf-8" ?>
<mod:subpolis pc="W">
<mod:aantalstappenafbouwregeling>0</mod:aantalstappenafbouwregeling>
<mod:afsluitprovisie>0</mod:afsluitprovisie>
<mod:afsluitprovisieperc>0</mod:afsluitprovisieperc>
<mod:afsluitprovisiepercproducent>0</mod:afsluitprovisiepercproducent>
<mod:afsluitprovisieperctp>0</mod:afsluitprovisieperctp>
<mod:afsluitprovisieproducent>0</mod:afsluitprovisieproducent>
<mod:omsproductcode>Uitgebreide gevarenverzekering</mod:omsproductcode>
<mod:omssoortverzekering>Brand</mod:omssoortverzekering>
<mod:pakketkorting>0</mod:pakketkorting>
<mod:prolongatiepremieperjaar>255.56</mod:prolongatiepremieperjaar>
<mod:prolpremieexclpakketkorting>63.89</mod:prolpremieexclpakketkorting>
<mod:promillagedooreen>1.28</mod:promillagedooreen>
<mod:soortpolis>0</mod:soortpolis>
<mod:soortverzekering>BR</mod:soortverzekering>
<mod:tekencommissie>7.39</mod:tekencommissie>
<mod:tekencommissieperc>0</mod:tekencommissieperc>
<mod:tekencommissieperctp>0</mod:tekencommissieperctp>
<mod:tekencommissietp>0</mod:tekencommissietp>
<mod:toekomstprovisie>0</mod:toekomstprovisie>
<mod:transactiecode>0</mod:transactiecode>
<mod:transactiestatus>In behandeling</mod:transactiestatus>
<mod:verzekerdbedrag>165000</mod:verzekerdbedrag>
<mod:vrijveld10>0</mod:vrijveld10>
<mod:vrijveld13>0</mod:vrijveld13>
<mod:vrijveld14>0</mod:vrijveld14>
<mod:vrijveld6>0</mod:vrijveld6>
<mod:vrijveld7>0</mod:vrijveld7>
<mod:vrijveld8>0</mod:vrijveld8>
<mod:vrijveld9>0</mod:vrijveld9>
<mod:clausule pc="W">
<mod:internclausulenummer>1</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>504</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>505</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>512</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>692</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>692</mod:internclausulenummer>
</mod:clausule>
<mod:clausule pc="W">
<mod:internclausulenummer>1311</mod:internclausulenummer>
</mod:clausule>
<mod:conditie pc="W">
<mod:internconditienummer>187</mod:internconditienummer>
</mod:conditie>
<mod:mijverdelingpolis pc="W">
<mod:maatschappijnummer>VN013</mod:maatschappijnummer>
</mod:mijverdelingpolis>
<mod:polisvrij pc="W">
<mod:revisienummer>0</mod:revisienummer>
<mod:rubriek1>Royement i.v.m. opzegging</mod:rubriek1>
</mod:polisvrij>
<mod:tekstpolis pc="W">
<mod:bloknummer>1</mod:bloknummer>
<mod:paginanummer>1</mod:paginanummer>
<mod:revisienummer>0</mod:revisienummer>
</mod:tekstpolis>
<mod:acceptatiepunten>0</mod:acceptatiepunten>
</mod:subpolis>
13
Digital Signatures / Re: Signing XML with smartcard(private key not exportable)
« Last post by stary on June 02, 2018, 08:39:02 AM »I was excited reading the new version (9.5.0.73) Release Notes:
I am using Gemalto K30 USB hardware token, where some certificates are stored.
I've just tried new version ActiveX, but there is still the same problem as it was in previous version.
I can read public key with Cert.ExportPublicKey() method, but not the private key with Cert.ExportPrivateKey() method.
This is what I get from Cert.LastErrorText property:
Is there a possible solution for this?
Quote
XmlDSigGen Now capable of using non-exportable private keys on Windows, such as for A3 certificates where the private key is on a hardware token.
I am using Gemalto K30 USB hardware token, where some certificates are stored.
I've just tried new version ActiveX, but there is still the same problem as it was in previous version.
I can read public key with Cert.ExportPublicKey() method, but not the private key with Cert.ExportPrivateKey() method.
This is what I get from Cert.LastErrorText property:
Code: [Select]
ChilkatLog:
ExportPrivateKey:
DllDate: May 22 2018
ChilkatVersion: 9.5.0.73
UnlockPrefix: NONE
Architecture: Little Endian; 32-bit
Language: ActiveX
VerboseLogging: 0
exportPrivateKey:
Failed to export private key.
The private key is not exportable from the Windows protected store.
--exportPrivateKey
Failed.
--ExportPrivateKey
--ChilkatLog
Is there a possible solution for this?
14
.NET / Re: How to check existing directory faster on FTP server
« Last post by Rajnishsmu on June 01, 2018, 03:27:51 AM »Hi dev
I have to upload Directory recursively on FTP server using Chilkat.Ftp2 class and ftp.LargeFileUpload() method.
We are checking directory via loop,checking wether the directory exist or not which is taking too much time.
So we need to check entire directory faster. Can you please suggest any chilkat method or propertis to check existing directory.
I have to upload Directory recursively on FTP server using Chilkat.Ftp2 class and ftp.LargeFileUpload() method.
We are checking directory via loop,checking wether the directory exist or not which is taking too much time.
So we need to check entire directory faster. Can you please suggest any chilkat method or propertis to check existing directory.
15
.NET / Re: How to check existing directory faster on FTP server
« Last post by dev guy on May 31, 2018, 06:17:07 PM »Have you thought about downloading the directory tree to xml (.DirTreeXml) and parsing that?
16
Android / Re: Android Java App crashes on loading chilkat library
« Last post by Rudiment on May 30, 2018, 06:43:00 AM »I figured out all is working well as long as I am on a device that is below armv8a.
But i did add the latest library and java (com) to the project (armv8a).
The app crashes if i create my apk file and start it after i did install on my device
(Samsung S7 Android 7.0 Armv8a) directly via apk.
If I install from compiler directly (with active debugging) it does not crash and is installed correctly.
For J5 and other phones it works. But they are using armv7a mainly!
But i did add the latest library and java (com) to the project (armv8a).
The app crashes if i create my apk file and start it after i did install on my device
(Samsung S7 Android 7.0 Armv8a) directly via apk.
If I install from compiler directly (with active debugging) it does not crash and is installed correctly.
For J5 and other phones it works. But they are using armv7a mainly!
17
.NET / How to check existing directory faster on FTP server
« Last post by Rajnishsmu on May 29, 2018, 09:03:22 AM »Hello,
To create log file for our FTP project, for each file and folder we are using chilkat dll for upload directory through ftp.LargeFileUpload() method. Here we are checking that the directory is exist or not in FTP server, into the For loop via ftp.ChangeRemoteDir() method. This process is taking too much time to check the existing directory.Is there any other way to find out the same which will take less time to check existing directory.
To create log file for our FTP project, for each file and folder we are using chilkat dll for upload directory through ftp.LargeFileUpload() method. Here we are checking that the directory is exist or not in FTP server, into the For loop via ftp.ChangeRemoteDir() method. This process is taking too much time to check the existing directory.Is there any other way to find out the same which will take less time to check existing directory.
18
REST / HTTP / HTTPS / Re: Default value of AwsSignatureVersion is 4 not 2
« Last post by Danne on May 29, 2018, 04:19:37 AM »FWIW: I just discovered that this is documented in the release notes.
19
Email Protocols / Re: Chilkat.Imap - One long running instance or short lived ones as needed?
« Last post by Chilkat on May 25, 2018, 02:46:26 PM »I think keeping the connection long-term is the best way to go. It might be a good idea to call imap.Noop once every few minutes when there is no activity.
20
Email Protocols / Chilkat.Imap - One long running instance or short lived ones as needed?
« Last post by will.blackburn on May 25, 2018, 12:05:20 PM »Apologies if this seems an obvious answer... 
... But I've been trying to work out if it's better to create a single long lived instance of the Imap object that exists over the entire Program or Thread/Task or if I should create an instance at the time I need the email information during the programming process.
Thinking it through and reading the RFC documents, I believe that a long running instance is the way to do it as long as the connection is kept alive or checked and re-connected to as required, but there isn't a clear explanation that I've found and each of the examples always Chilkat gives only show a single process with no reference as to how much "work" is acceptable for the instance.
Any pointers or advice or just confirmation would be great...
... But I've been trying to work out if it's better to create a single long lived instance of the Imap object that exists over the entire Program or Thread/Task or if I should create an instance at the time I need the email information during the programming process.
Thinking it through and reading the RFC documents, I believe that a long running instance is the way to do it as long as the connection is kept alive or checked and re-connected to as required, but there isn't a clear explanation that I've found and each of the examples always Chilkat gives only show a single process with no reference as to how much "work" is acceptable for the instance.
Any pointers or advice or just confirmation would be great...