On Thu, Jun 11, 2009 at 7:05 AM, Onno Scheffers wrote:
> ${} is a shortcut to make it very easy to insert some property-value into
> your template without having to use a component for it. There are typically
> 3 ways to insert some content into your page:
>
> 1. The way you're using components,
${} is a shortcut to make it very easy to insert some property-value into
your template without having to use a component for it. There are typically
3 ways to insert some content into your page:
1. The way you're using components, keeping most of the configuration in the
Java class:
Some title
@
Hi all.
As I know from My experiments, ${ ... } converts each object to string,
in contrast to "prop:...", which returns object "as is". In page link,
this difference should not take an effect. But in parameters this is
significant ...
Kai Weber napsal(a):
> Hi,
>
> I am a Tapestry beginner. I a
${...} expansions evaluate the expression and convert it to a string.
Since the page parameter expects a string, that's OK.
Converting a context (an array or List to a string) is different than
passing the List, unchanged, as the context parameter.
Allowing ${...} expansions in attribute values
Hi,
I am a Tapestry beginner. I am far from knowing all the internals. I use
the PageLink component in one of my as follows:
@Component(id="backLink",
parameters={
"page=${backLink}",
"context=backLinkContext",
"anchor=${prev.getUniqueIdentifier()}"})
private PageLink backLink;
My quest
