You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Wendy Smoak <We...@asu.edu> on 2003/06/23 23:04:26 UTC

Living in a frame

So far I've resisted, but I have a feeling my next Struts app is going to
get sucked into a frame.  The department that handles "the website" likes to
appropriate content, and of course it looks more unified if things don't pop
out into their own browser window like I'm doing now.  They handle the
static HTML with IIS, and there's a separate server running Apache/Tomcat
that serves up the Struts apps.

So... If they insist on stuffing my Struts webapp into a frame instead of
targeting a new window for me, is there anything I should be aware of?  I'm
concerned about the jsessionid, about how the tabbed tiles are going to
work, etc.  I know the real answer is to just try it, but I wondered if
anyone had any advice up front.

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Public Affairs, Information Resources Management
Arizona State University, Tempe AZ 

Re: Living in a frame

Posted by Erik Price <ep...@ptc.com>.

Wendy Smoak wrote:
> So far I've resisted, but I have a feeling my next Struts app is going to
> get sucked into a frame.  The department that handles "the website" likes to
> appropriate content, and of course it looks more unified if things don't pop
> out into their own browser window like I'm doing now.  They handle the
> static HTML with IIS, and there's a separate server running Apache/Tomcat
> that serves up the Struts apps.

Using a different frame sounds better than using a new window, IMHO.

> So... If they insist on stuffing my Struts webapp into a frame instead of
> targeting a new window for me, is there anything I should be aware of?  I'm
> concerned about the jsessionid, about how the tabbed tiles are going to
> work, etc.  I know the real answer is to just try it, but I wondered if
> anyone had any advice up front.

I can't speak to the tiles question, but there shouldn't be any real 
difference -- the JSESSIONID is propagated by either the cookie or by 
the URLs encoded into your hyperlinks, and these will still exist if 
you're using frames.  The only links that will not propagate the ID are 
the ones in the frame generated by IIS, but I'm sure you have dealt with 
a similar issue in the previous setup where the IIS content was in 
another window.


Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org