You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jorg Heymans <jh...@domek.be> on 2003/12/13 23:18:37 UTC
2.1x equivalent code
In 2.0 i would do the following to always cache a component
public CacheValidity generateValidity() {
return NOPCacheValidity.CACHE_VALIDITY;
}
What is the 2.1x equivalent for this? (i'm writing a caching request
generator)
public SourceValidity getValidity() {
return ??;
}
thanks
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Syntax
Posted by Christian Haul <ha...@informatik.tu-darmstadt.de>.
Damon van Opdorp wrote:
> Hi All,
>
> I'm trying to use a parameter to specify which action set to use in a
> pipeline as below:
>
> ...
> <map:match pattern="*/*/*.xhtml">
> ...
> <!-- perform page specific actions -->
> <map:act set="{3}-actions" />
> ...
>
> The parameter doesn't seem to be getting substituted, as I get the
> error:
>
> Unknown action-sets named '{3}-actions' at file:...
>
> Does the act component support substitution? Any workarounds or
> suggestions on where to fix?
No, it does not. Workarounds are to use a selector with hasrd coded
actions, an action-set or a MultiAction that can fire different methods
based on a parameter.
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Syntax
Posted by Damon van Opdorp <da...@sol.deeper.co.nz>.
Hi All,
I'm trying to use a parameter to specify which action set to use in a
pipeline as below:
...
<map:match pattern="*/*/*.xhtml">
...
<!-- perform page specific actions -->
<map:act set="{3}-actions" />
...
The parameter doesn't seem to be getting substituted, as I get the
error:
Unknown action-sets named '{3}-actions' at file:...
Does the act component support substitution? Any workarounds or
suggestions on where to fix?
Cheers,
Damon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
AW: 2.1x equivalent code
Posted by Marco Rolappe <m_...@web.de>.
hi jorg,
> -----Ursprungliche Nachricht-----
> Von: users-return-59879-m_rolappe=web.de@cocoon.apache.org
> [mailto:users-return-59879-m_rolappe=web.de@cocoon.apache.org]Im Auftrag
> von Jorg Heymans
> Gesendet: Samstag, 13. Dezember 2003 23:19
> An: users@cocoon.apache.org
> Betreff: 2.1x equivalent code
>
>
> In 2.0 i would do the following to always cache a component
>
> public CacheValidity generateValidity() {
> return NOPCacheValidity.CACHE_VALIDITY;
> }
>
> What is the 2.1x equivalent for this? (i'm writing a caching request
> generator)
>
> public SourceValidity getValidity() {
> return ??;
> }
it's org.apache.excalibur.source.impl.validity.NOPValidity.SHARED_INSTANCE.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org