You can probably use Blocks to return the partial page updates, e.g.
in your template
<t:block t:id="fooBlock">
Some content here
</t:block>
In your page class
@Inject
private Block fooBlock
Object onSomeEvent() {
return fooBlock
}
Technically, it's the easiest if your blocks are defined on the same page
(as described above). However, if they're on a different page or component
template, you can use some of the ideas from Taha's blog (
http://tawus.wordpress.com/2011/04/20/tapestry-magic-3-plugin-blocks/ ) to
retrieve the blocks from the "other" page and render them on yours in
response to the event.
Cheers,
Alex K
On Thu, Jul 19, 2012 at 9:32 AM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Thu, 19 Jul 2012 06:02:34 -0300, Lance Java <lance.j...@googlemail.com>
> wrote:
>
> Returning a Page class tells tapestry to redirect to that page. I think
>> that you want to extract the page logic / tml into a component and then use
>> the component in two places.
>>
>
> Exactly. Otherwise, you'd need to access part of a page's template in
> another page, and that's something completely against Tapestry's philosophy
> and architecture.
>
> --
> Thiago H. de Paula Figueiredo
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
