This JIRA item is about page redirect parameters?
It's about a very small but helpful improvement to the LinkDecorator, to
be able to work with parameters, e.g. when "linking" elements form a
table to pages:
1. the source (the column/cell in the table) has one name to get it's
value(e.g. "toProduct.toProducer.name" for a column),
2. but in the target/destination(the parameter in the page - can be
autobound) page has a different one (e.g. /detail.htm?name=myname).
Without this small improvement, when using a LinkDecorator,
the call to the target page would be, e.g.
/detail.htm?toProduct.toProducer.name=myname
and that's really not working with Java and the Click autobinding.
I hope this helps. I can give you more examples if you need.
On Thu, May 21, 2009 at 10:19 PM, Adrian A. <[email protected]> wrote:
#3 - https://issues.apache.org/jira/browse/CLK-536
The implementation was suggested by a former Click commiter.
(Mostly in "hello world" like examples, a Table will display only one
Entity. In commercial ones, Table columns need to span to other Entity
properties too - this patch simplifies greatly this - without this, the
Table would need another TransferObject - with it, it can use directly
those
Entites, and have operations on them, since the "alias" allows it)
Which JIRA item are you referring to here?
CLK-536 is the issue. And there's the patch too.
How to implement it, was suggested at the link inside the issue.
(and other posts on the list around that time)
