Struts / Tiles Caching No Frames and Inter Tile communication

[Norm]

Hi all, We are considering using a struts/tiles approach for a new project. Its 
assumed its going to have a portal look and feel to it i.e. lots of seperate 
little windows providing distinct functionality. I want to avoid using frames, 
but I am very concerned with refreshing the whole screen when an interaction is 
only with 1 window. Is there any tile caching mechanism available, or, should 
we develop some sort of cache before we go to the business tier so we can 
redraw all of the tiles anyway? I would like to make a tile sticky when the 
app knows there is no need to refresh it on any particular interaction. Leading 
on from this, is there any nice mechanisms for inter tile communication? This 
is when 1 tile might want to alert another tile about an event. Thanks for any 
help. Norm


Broadband interface (RIA) + mail box saftey = 
http://Struts_User_List.roomity.com
*Your* clubs, no sign up to read, ad supported; try broadband internet. 

Re:

[Norm Deane]

You should check out sitemesh. It uses page decoration (vs Tiles page 
composition) and requires very little configuration and programming 
overhead. It also is capable of decorating pages with elements from 
other sites/applications.


http://opensymphony.com/sitemesh/

Norm

 wrote:

On 6/30/05, Aleksandar Matijaca [EMAIL PROTECTED] wrote:


On 6/30/05, Wendy Smoak [EMAIL PROTECTED] wrote:


From: Bill Schneider [EMAIL PROTECTED]


Tiles is very powerful but I've found that 99% of the time I'm only using
it to wrap a page in a consistent layout/navigation. It seems like I'm
not getting enough value out of it to justify the additional layer of
indirection of having to touch tiles-defs.xml. I also would love to be
able to include header/footer pages from another webapp context.


What about plain-old jsp includes? Maybe they're enough for your needs.



I believe that if you are using JSP includes, the included file, looses
any objects that were put in using request.setAttribute(...) ? I have found
that using jsp:includes is typicaly good enough to include any group page
imports, definitions and maybe any JavaScript...



Maybe this example can help you decide, if jsp:include is sufficient
for you: 
http://struts.sourceforge.net/strutsdialogs/dialogaction-logincontrolsample.html

It has link to this live demo (can be offline from time to time, since
this is a shared Tomcat):
http://www.superinterface.com/strutsdialog/embeddedmasterpage-tomcat.do

The Sign In box is an included Struts component. Notice, that it
knows nothing about master page, and master page knows nothing about
the component.

Michael.

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