Vjeran, thanks a lot.
I am really surprised to see that line
"Link link = pageRenderLinkSource.createPageRenderLink( page.getClass() );"
indeed passes page context! I see this is documented
http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/services/PageRenderLinkSource.html
Page.configured(user.getId());
}
...and in template:
Edit
...instead of shorter, but type-nonsafe:
context="user.id">Edit
Cheers,
Vjeran
- Original Message -
From: "Vjeran Marcinko"
To: "Tapestry users"
Sent: Sunday, June 21, 2009 1:14 PM
Subject
try users"
Sent: Sunday, June 21, 2009 10:32 AM
Subject: Re: Type-safe PageLink version
I usually use something like this:
@Component(parameters = { "page=prop:editEmployeePage", "context=prop:
employee.id })
private PageLink pageLink;
@Inject
private ComponentC
I usually use something like this:
@Component(parameters = { "page=prop:editEmployeePage", "context=prop:
employee.id })
private PageLink pageLink;
@Inject
private ComponentClassResolver resolver;
@Cached
public String getEditEmployeePage() {
resolver.resolvePageClassNameToPageName(EditEmploy
Hello,
I have an idea for PageLink version that would be type-safe because I simply
love when I don't have to worry about page names or context parameters in my
templates as much as possible, especially cosidering that I like to refactor
much...
If PageLink could accept page *instance* as pa
