>Ok, I see.
>Here is my new code:
>public Serializable getKey() {
> return objekt+objekt_ID+geb_ID+stock_ID+abweichungen+suchtyp;
> }
Well, I don't see the rest of your code, but certainly would not do it like
this:
You just do something like:
protected String cacheKey = null;
public void setup(SourceResolver resolver, Map objectModel, String src,
Parameters parameters){
.....
.....
.....
cacheKey = someconstructedcachekeydependingonparamtersforexample
}
public Serializable getKey() {
return cacheKey;
}
Now, in very short, cocoon does the setup() of your generator, creating the
cacheKey, then does a getKey(), if it finds one that matches, it checks your
getValidty() and if that also matches gives you your cached output (I left out
some steps, but these are the important ones)
Also notice, that for checking the validity of the cache, cocoon always does
the component setup(). Make sure, that the component setup() does not involve
heavy objects creations, since this implies havy cachekey lookups for cocoon
AS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
