FW: [Arsperl-users] ars_Export failure
Brought to you by:
jeffmurphy
Menu
▾
▴
FW: [Arsperl-users] ars_Export failure
|
From: Mark V. <Mar...@ev...> - 2005-05-27 18:05:38
|
I did some investigation: =20 NOTE: The following is applicable to ARS.xs for version 1.83. Similar functionality may exist in previous versions. =20 The arsExport API call is expecting a parameter, *lockInfo, as the fifth parameter. The documentation also says that, if no encryption is desired, pass a NULL. The ARSperl routine ars_Export is passing an ARWorkflowLockStruct parameter (*lockInfo) but is not putting any data into it (neither the lockType nor lockKey elements). This is what the error is complaining about. If the parameter passed is changed to a NULL, the routine returns an unencrypted version of the export and looks the same as if exporting from the Admin tool. If I set lockInfo.lockType =3D AR_LOCK_TYPE_NONE, the data does not get locked but= still gets encrypted. =20 I am not sure of the encryption intent of the routine, but the easiest way to remedy the situation is to change line 2250 in ARS.xs and recompile: Old: &workflowLockStruct, New: NULL, NOTE: The declaration of workflowLockStruct could also be removed (see lines 2109-2111 in version 1.83). =20 This would make the output unencrypted. =20 Additional work could be done to allow the end user to choose encryption by adding a parameter to the call. =20 Thoughts? =20 Thanks, Mark =20 Mark Vaughan Programmer III =20 Direct: +1 303 802 2426 Cell: +1 303 601 4434 Fax: +1 303 802 1420 mar...@ev... <mailto:mar...@ev...>=20 Evolving Systems, Inc.=20 9777 Pyramid Court, Suite 100, Englewood, CO USA 80112 www.evolving.com ________________________________ From: ars...@ar... [mailto:ars...@ar...] On Behalf Of Steve McDonald Sent: Thursday, May 26, 2005 12:05 PM To: ars...@ar... Subject: RE: [Arsperl-users] ars_Export failure =20 Any luck on this? I get the same thing when I run it manually. The error message guide says to set the lock level to one of the following: =20 - AR_LOCK_TYPE_NONE(0) - AR_LOCK_TYPE_READONLY(1) - AR_LOCK_TYPE_HIDDEN(2) =20 Where do I set this and what is the syntax? ________________________________ From: ars...@ar... [mailto:ars...@ar...] On Behalf Of Mark Vaughan Sent: Wednesday, May 25, 2005 1:31 PM To: ars...@ar... Subject: [Arsperl-users] ars_Export failure All, Has anyone gotten the ars_Export routine to not throw errors and, if so, is the data returned encrypted? =20 I'm getting the following errors when running the t/02export.t test case: >> /usr/bin/perl -Iblib/arch -Iblib/lib -I/usr/local/lib/perl5/5.6.1/sun4-solaris -I/usr/local/lib/perl5/5.6.1 t/02*.t =20 1..8 ok [1] schema><ARSperl Test not ok [2] ([ERROR] Unknown object lock level specified (ARSperl Test) (ARERR #8832)) schema><ARSperl Test2 not ok [3] ([ERROR] Unknown object lock level specified (ARSperl Test2) (ARERR #8832)) schema><ARSperl Test-join not ok [4] ([ERROR] Unknown object lock level specified (ARSperl Test-join) (ARERR #8832)) filter><ARSperl Test-Filter1 not ok [5] ([ERROR] Unknown object lock level specified (ARSperl Test-Filter1) (ARERR #8832)) active_link><ARSperl Test-alink1 not ok [6] ([ERROR] Unknown object lock level specified (ARSperl Test-alink1) (ARERR #8832)) escalation><ARSperl Test-escalation1 not ok [7] ([ERROR] Unknown object lock level specified (ARSperl Test-escalation1) (ARERR #8832)) char_menu><ARSperl Test-menu-search1 not ok [8] ([ERROR] Unknown object lock level specified (ARSperl Test-menu-search1) (ARERR #8832)) =20 Thanks, Mark =20 Mark Vaughan Programmer III =20 Direct: +1 303 802 2426 Cell: +1 303 601 4434 Fax: +1 303 802 1420 mar...@ev... <mailto:mar...@ev...>=20 Evolving Systems, Inc.=20 9777 Pyramid Court, Suite 100, Englewood, CO USA 80112 www.evolving.com =20 This e-mail and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform Evolving Systems TIS at ti...@ev... and then delete the e-mail from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. To ensure regulatory compliance and for the protection of our clients and business, Evolving Systems may monitor and read e-mails sent to and from its servers. Although Evolving Systems routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Evolving Systems makes no representation or warranty as to the absence of viruses in this e-mail or any attachments. Registered Office: 9777 Mt. Pyramid Ct Suite 100, Englewood, CO 80112=20 This e-mail and any attachments may be confidential and/or legally privil= eged. If you have received this e-mail and you are not a named addressee,= please inform Evolving Systems TIS at ti...@ev... and then delete t= he e-mail from your system. If you are not a named addressee you must not= use, disclose, distribute, copy, print or rely on this e-mail. To ensure= regulatory compliance and for the protection of our clients and business= , Evolving Systems may monitor and read e-mails sent to and from its serv= ers. Although Evolving Systems routinely screens for viruses, addressees = should scan this e-mail and any attachments for viruses. Evolving Systems= makes no representation or warranty as to the absence of viruses in this= e-mail or any attachments.=20 Registered Office: 9777 Mt. Pyramid Ct Suite 100, Englewood, CO 80112 |
