[mailto:d...@me.com]
Sent: Friday, December 11, 2009 3:53 PM
To: user@ofbiz.apache.org
Subject: Re: Query about Cache in groovy
By default there is a timeout on this cache.
-David
On Dec 11, 2009, at 4:20 AM, Pankaj Jain wrote:
Hi
In ofbiz, when we use a groovy file , in ist call to groovy, .g
@ofbiz.apache.org
Subject: Re: Query about Cache in groovy
By default there is a timeout on this cache.
-David
On Dec 11, 2009, at 4:20 AM, Pankaj Jain wrote:
> Hi
>
> In ofbiz, when we use a groovy file , in ist call to groovy, .groovy file is
> read and parsed and then we store the generate
But it is taking expire time as 0, that means the component in cache will never
expire.
-Original Message-
From: David E Jones [mailto:d...@me.com]
Sent: Friday, December 11, 2009 3:53 PM
To: user@ofbiz.apache.org
Subject: Re: Query about Cache in groovy
By default there is a timeout
By default there is a timeout on this cache.
-David
On Dec 11, 2009, at 4:20 AM, Pankaj Jain wrote:
> Hi
>
> In ofbiz, when we use a groovy file , in ist call to groovy, .groovy file is
> read and parsed and then we store the generated class file in a cache and
> after that for every next c
Hi
In ofbiz, when we use a groovy file , in ist call to groovy, .groovy file is
read and parsed and then we store the generated class file in a cache and after
that for every next call to groovy, we refer the cache to get the class file.
But if we update the .groovy files at run time, the chang
