>> > > org.foo.pages.Start does not contain an embedded component with id
>> > > 'apple'.
>> > >
>> > > Does it expect me to have a tag in the page even though
>> I'm
>> > > delegating the rend
In fact, BeanEditForm and Grid suffer from the same problem, and a fix will
be forthcoming.
Basically, there will be a configuration point for contributing page names,
and matching them up to (in BeanEditForm/Grid) various property types.
The same pattern can hold; define new pages, contribute a
Howard Lewis Ship wrote:
> This is very easy in Tapestry; just put the components on another page,
> inject the page, and choose the component from that page.
And how to deal with actionlink's inside the component/block from
another page? All actions will go to the page the component/block
belongs
return null;
}
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 4:08 PM
To: Tapestry users
Subject: Re: T5: Best practice for rendering a dynamic component
Absolutely. You can put it inside a to keep it from rendering
normally.
om: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 4:08 PM
To: Tapestry users
Subject: Re: T5: Best practice for rendering a dynamic component
Absolutely. You can put it inside a to keep it from rendering
normally.
On 5/23/07, Joel Wiegman <[EMAIL PROTECTED]>
expect me to have a tag in the page even though I'm
> > delegating the rendering of it?
> >
> > -Original Message-
> > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, May 23, 2007 1:41 PM
> > To: Tapestry users
> > Subject:
gt;
> -Original Message-
> From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 23, 2007 1:41 PM
> To: Tapestry users
> Subject: Re: T5: Best practice for rendering a dynamic component
>
> The Delegate component is what you need:
>
>
>
> @Comp
ect: Re: T5: Best practice for rendering a dynamic component
The Delegate component is what you need:
@Component
private Apple apple;
@Component
private Banana banana;
public Object getFruit() {
if ( ... ) return apple;
return banana;
}
With Tapestry, the construction of pages is stati
ing the rendering of it?
-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 1:41 PM
To: Tapestry users
Subject: Re: T5: Best practice for rendering a dynamic component
The Delegate component is what you need:
@Component
private Appl
The Delegate component is what you need:
@Component
private Apple _apple;
@Component
private Banana _banana;
public Object getFruit() {
if ( ... ) return _apple;
return _banana;
}
With Tapestry, the construction of pages is static, fixed, unchanging, much
like the construction of your cla
10 matches
Mail list logo
