Hi all, Compiere developers!
Data caching for AD is great functionality of Compiere but is quite boring during development of AD, because you always have to run 'Cache Reset' process to let changes take effect on testing client.
Does anybody knows if cache can be disabled (at least during development, even if it requires some kind of java coding) or if there is any other trick?!
Thanks in advance & best regards,
> Does anybody knows if cache can be disabled
Yes, Tools -> Preference -> Cache Windows.
Carlos Ruiz - globalqss
I already heard about this item on preference window but I can't find it!!!
maybe it comes from a specific version.. which version are you using, Carlos?
I'm currently using 2.5.3a
It's true, in 2.5.3a the Cache on Client was not implemented.
What you are having is the Cache on Server.
Try to connect without application server, this is:
- in the connection window of Compiere click the button in front of Host field
- give a "dummy" application server and push "Test Application Server" button
- then fill manually the database fields (possibly already filled) and push "Test Database"
- then push OK button
- in the Host field must appear the dummy app server
This way the connection is slightly slow, but works as you want.
hhhmmm.. unfortunately it does not work..
I also try with application server stopped but cache "is still there". IOW changes to AD or to print format are not seen until I manually reset the cache (this is quite boring because you have to close ALL the other windows opened before do a cache reset)
any other clue for version 2.5.3a?
> IOW changes to AD or to print format are
> not seen until I manually reset the cache
Excuse me, my instructions were for window cache, you didn't mention that your problem is with print format :-(
And yes, I'm developing an invoice format, and sometimes changes to print format are taken directly, but some times I must close all Compiere to get the changes (even Cache reset doesn't work at some times for me with print formats!)
Sorry I can't help you more with this issue.