This will not work, at least, not always. It certainly won't understand about
page activation context.
Sent from my iPad
On Jul 26, 2012, at 9:37 AM, Alex Kotchnev <akoch...@gmail.com> wrote:
> Ozkan - just an idea - it seems that you might be able to do something like
> this :
>
> @Inject
> private ComponentResources compResources
>
> @Property
> String editPath
>
> page = compResources.getPage()
> editPath =
> page.getComponentResources().getBaseResource().forPath("edit").getPath()
>
> then, in your component, you'd use something like this :
> <t:pageLink t:page="prop:editPath">Edit</t:pageLink>
>
> And of course, this is totally not tested or guaranteed to work - I'm just
> looking at the API (
> http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/ComponentResources.html
> ).
>
> Cheers,
>
> Alex K
>
> On Thu, Jul 26, 2012 at 8:12 AM, ZKN __ <z...@abv.bg> wrote:
>
>>
>> Hi,
>> I have a component that's to be included in different pages. Inside the
>> component I have page links that need to be relative to the current page.
>> Something like this:
>> <t:pagelink class="btn" page="./Edit" context="[ID]">
>>
>> <span><span>${message:edit}</span></span>
>> </t:pagelink>
>> The page link should point to different pages according to the current
>> page.
>> Is that possible?
>>
>>
>> Thanks,
>> Özkan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
