Do you not just need to use literal: prefix on your string? Otherwise Tapestry assumes it is a property. So how about...
<t:pageLink page="item/project" context="literal:add">Add a project</t:pageLink> Just a guess from reading http://tapestry.apache.org/tapestry5/guide/parameters.html CTRL-F "Binding Expressions" Cheers Russell -----Original Message----- From: Luther Baker [mailto:[EMAIL PROTECTED] Sent: 09 September 2008 05:41 To: Tapestry users Subject: Re: pageLink and a context Sorry, lets try that again: If I supply a number as the context: <t:pageLink page="item/project" context="*2*">Pick a project ...</t:pageLink> All is well and the url looks like ... /issues/item/project/1 But if I supply text - the application breaks. <t:pageLink page="item/project" context="*add*">Add a project ...</t:pageLink> | .... Exception: ..... Home does not contain a property named 'one' "Home" is the name of the page this link code on. Is context required to be a number? That brings up another question -- unfortunately, I am heavily schooled in the Struts and Spring MVC way and often, I would use the same controller for related functions and just pass a parameter to "do the right thing". So, what I was doing here was something like: .../project?create .../project?search But - I'm guessing I shouldn't even be doing this. I should just go to project/create and project/search and then piece together the components. I shouldn't even try to share things like a controller because it just doesn't work that way. Or - per the tutorial I just read ... this should probably be a <t:actionLink .... Does that sound correct? In general, how should one navigate when you need to go to a page that needs to do a little prep (db retrieval, etc) Many thanks - getting more productive everyday. -Luther On Mon, Sep 8, 2008 at 11:30 PM, Luther Baker <[EMAIL PROTECTED]> wrote: > If I supply a number as the context: > > <t:pageLink page="item/project" context="*2*">Pick a project > ...</t:pageLink> > > All is well and the url looks like ... > > > But if I supply text - the application breaks. Is context required to be a > number? > > <t:pageLink page="item/project" context="*add*">Add a project > ...</t:pageLink> | > > Home does not contain a property named 'one' > -Luther > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]