Re: Best Practices for static content

2005-06-17 Thread Andreas Toom
Can't you use a TilesController-class and manipulate your 
tiles-attribute depending on some parameter in request scope?.

Doing so you only have to declare one action and one tiles-definition.

/Andreas

Ramadi Pearse wrote:

Does anyone have best practices on how to compose or
decorate stand-alone static content? It seems overkill
to have to modify tile-defs.xml for each new static
page I want to add to the website. Is SSI or SiteMesh
more appropriate here? By the way, this is to
complement a web app which already uses Tiles to
compose the data portion of the app. Thanks!



__ 
Discover Yahoo! 
Have fun online with music videos, cool games, IM and more. Check it out! 
http://discover.yahoo.com/online.html


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Best Practices for static content

2005-06-16 Thread Ramadi Pearse
David,

I don't have any exceptionally long files. I remember
Rick Reumann saying on this list too that he dumped
SiteMesh in favor of Tiles because of the buffering
problem. I never heard of anyone running
Tiles/SiteMesh together, although it is feasible. 

Maybe I will just stick to creating tile definitions
for my pages. It can't hurt - but I wish someone from
the Struts team could tackle my question too. Someone
must have professionally encountered the same problem
I have.

Thanks.

--- "David G. Friedman" <[EMAIL PROTECTED]> wrote:

> Dear Ramadi,
> 
> I would recommend using SiteMesh (it's a filter)
> while you continue using
> Struts & Tiles.
> 
> If you have any exceptionally large pages you wish
> to display (i.e. pages
> and pages and pages of content) you might want to
> watch out for String
> buffer issues.  Why?  SiteMesh receives a complete
> page before quickly
> parsing it and wrapping it per it's configuration. 
> The result is that TRULY
> large pages might blow a string buffer limit.  In
> practical use that may
> never happen but if you have a heavy amount of
> tables and/or long pages, the
> string buffer size might become an issue.  Do I know
> what that size limit
> might be?  No.  I just read about it while
> researching and testing out
> SiteMesh a few months ago and thought I'd provide a
> warning, just in case.
> After all, you never know how much people will
> write.
> 
> Regards,
> David
> 
> -Original Message-
> From: Ramadi Pearse [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 16, 2005 5:30 PM
> To: user@struts.apache.org
> Subject: Best Practices for static content
> 
> 
> Does anyone have best practices on how to compose or
> decorate stand-alone static content? It seems
> overkill
> to have to modify tile-defs.xml for each new static
> page I want to add to the website. Is SSI or
> SiteMesh
> more appropriate here? By the way, this is to
> complement a web app which already uses Tiles to
> compose the data portion of the app. Thanks!
> 
> 
> 
> __
> Discover Yahoo!
> Have fun online with music videos, cool games, IM
> and more. Check it out!
> http://discover.yahoo.com/online.html
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 




 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Best Practices for static content

2005-06-16 Thread David G. Friedman
Dear Ramadi,

I would recommend using SiteMesh (it's a filter) while you continue using
Struts & Tiles.

If you have any exceptionally large pages you wish to display (i.e. pages
and pages and pages of content) you might want to watch out for String
buffer issues.  Why?  SiteMesh receives a complete page before quickly
parsing it and wrapping it per it's configuration.  The result is that TRULY
large pages might blow a string buffer limit.  In practical use that may
never happen but if you have a heavy amount of tables and/or long pages, the
string buffer size might become an issue.  Do I know what that size limit
might be?  No.  I just read about it while researching and testing out
SiteMesh a few months ago and thought I'd provide a warning, just in case.
After all, you never know how much people will write.

Regards,
David

-Original Message-
From: Ramadi Pearse [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 16, 2005 5:30 PM
To: user@struts.apache.org
Subject: Best Practices for static content


Does anyone have best practices on how to compose or
decorate stand-alone static content? It seems overkill
to have to modify tile-defs.xml for each new static
page I want to add to the website. Is SSI or SiteMesh
more appropriate here? By the way, this is to
complement a web app which already uses Tiles to
compose the data portion of the app. Thanks!



__
Discover Yahoo!
Have fun online with music videos, cool games, IM and more. Check it out!
http://discover.yahoo.com/online.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Best Practices for static content

2005-06-16 Thread Ramadi Pearse
Wendy,

I need to put up some files that are long documents.
They won't change much, but are needed for the user.
Such are messages from the organization's president,
information about rules, legal info, etc. The
information will rarely change, but I need two
questions answered:

1) Is it the right thing to use tiles for this? Have
other people hard-coded static content with tiles?

2) What kind of internal directory structure did they
use under WEB-INF?

--- Wendy Smoak <[EMAIL PROTECTED]> wrote:

> From: "Ramadi Pearse" <[EMAIL PROTECTED]>
> > Does anyone have best practices on how to compose
> or
> > decorate stand-alone static content? It seems
> overkill
> > to have to modify tile-defs.xml for each new
> static
> > page I want to add to the website.
> 
> I see you asked a similar question that got no
> response.  Can you give an
> example of what you mean?  Is it something like
> magazine articles, where you
> want to draw the banners and menus, and then have
> the selected article as
> part of the page?
> 
> -- 
> Wendy Smoak
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 




__ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Best Practices for static content

2005-06-16 Thread Wendy Smoak
From: "Ramadi Pearse" <[EMAIL PROTECTED]>
> Does anyone have best practices on how to compose or
> decorate stand-alone static content? It seems overkill
> to have to modify tile-defs.xml for each new static
> page I want to add to the website.

I see you asked a similar question that got no response.  Can you give an
example of what you mean?  Is it something like magazine articles, where you
want to draw the banners and menus, and then have the selected article as
part of the page?

-- 
Wendy Smoak


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Best Practices for static content

2005-06-16 Thread Ramadi Pearse
Does anyone have best practices on how to compose or
decorate stand-alone static content? It seems overkill
to have to modify tile-defs.xml for each new static
page I want to add to the website. Is SSI or SiteMesh
more appropriate here? By the way, this is to
complement a web app which already uses Tiles to
compose the data portion of the app. Thanks!



__ 
Discover Yahoo! 
Have fun online with music videos, cool games, IM and more. Check it out! 
http://discover.yahoo.com/online.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]