hi,

could you post your page class? 

if you need some heavy preparation you could inject
the page and call some methods:

public class Page1()
{
    @InjectPage
    private Page2 page2;

    @Component
    private ActionLink page2Link 

   Object onActionFromPage2Link()
   {
      page2.heavyInit(...);

      return page2;
   }
}


public class Page2() {
    pubilc void heavyInit(...)  {}
 
}





"Luther Baker" <[EMAIL PROTECTED]> 
09.09.2008 06:41
Bitte antworten an
"Tapestry users" <users@tapestry.apache.org>


An
"Tapestry users" <users@tapestry.apache.org>
Kopie

Thema
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
>
>
>

Reply via email to