AW: Caching Fragments

[Till N. <til...@ne...>]

Hi Mike,

there are different approaches to perform the complete rendering of a
page:
- Use a simple JSP
- Forward to a tiles definition
  <action path=3D"/foo" forward=3D"tilesDefName" />
- Use an action forwarding to a JSP containing the different includes.

Regards,
Till

> -----Urspr=FCngliche Nachricht-----
> Von: Mike Aymard [mailto:Mik...@ga...]
> Gesendet: Donnerstag, 29. Januar 2004 18:33
> An: Till Nagel; act...@li...
> Betreff: RE: Caching Fragments
>=20
> Hi Till,
>=20
> Thanks for the reply. Breaking the page into includes makes sense and
I
> can create an action for each, but when an action forwards to a jsp
> snippet and that fragement only is rendered, how does the page as a
> whole get returned? Does there need to be a separate action that
> forwards to the jsp page containing the all of the jsp:include
> directives? Sorry for being so dense!
>=20
> Thanks,
> Mike
>=20
> -----Original Message-----
> From: Till Nagel [mailto:til...@ne...]
> Sent: Thursday, January 29, 2004 2:11 AM
> To: Mike Aymard; act...@li...
> Subject: Re: Caching Fragments
>=20
> Hi Mike,
>=20
> a common aproach is to assemble pages using tiles (or plain
jsp:include
> tags) and have multiple actions for various fragments. See
> http://jakarta.apache.org/struts/userGuide/building_view.html#includes
> for details. Then write an action for each fragment in order to
provide
> the correct caching info and forward to a jsp snippet that just
renders
> a single fragment.
>=20
>=20
>=20
>=20
>=20