Am Donnerstag, 31. Dezember 2009 schrieben Sie:
[...]

> What do you mean by "start aqbanking4"?
>
> Just starting an application linked against AqBanking4 doesn't create a
> working aqbanking4-configuration.
>
> The command "aqbanking-cli updateconf" is smarter than just to check
> whether the folder exists... It also checks whether there are users setup
> inside the aqbanking4 configuration. If there is none it tries to update
> from previous versions. If there already are users in the AqBanking4
> configuration the tool does nothing.
>
> However, I don't know whether your GnuCash version already tried to update
> the configuration.

This is from memory, but I am very sure that it is accurate:
I started gnucash, tried "Saldenabfrage" nothing happend, then I 
did "Aqbanking Einrichtungs-Assistenten starten" verified that no account is 
configured and aborted it again.

For sure, I did not enter any data.


[...]
> [...]
>
> It *is* an AqBanking function ("AB_" is the prefix for AqBanking
> functions), and I guess the patch by Micha *does* work.
>
> I only wanted to point out that AqBanking already provides simplified means
> to access AqBanking's certificate cache but that GnuCash can't use them due
> to its structure.

Ic

> The patch you referred to makes GnuCash access the cert cache directly
> which is also kind'a ok.

Can I dump the AqBanking's cert cache (to verify if the certs do not make it 
into the cache or if the cache lookup does not work for some reason).

> However, I guess it won't work with multiple AqBanking-applications working
> in parallel (which is currently a rare case, granted).

I can easily accept that restriction.

> If GnuCash could have used the class AB_Gui it wouldn't have to access the
> cache itself but could rather benefit from the advanced certificate
> management of AB_Gui).

I hope that gnucash 2.4.0 will use more AqBanking infrastructure instead of 
replicting code.

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Aqbanking-devel mailing list
Aqbanking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aqbanking-devel

Reply via email to