Hi, I have been working on a portal style collection of apps. There is a central app that functions as a simple content management tool. It generates dynamic Header, footer, navigation, etc... Other apps that are "in the portal" then do imports of the central application's Header/footer/nav.
The imports are in the jsp and look like this: <!--HEADER--> <bean:include href="http://localhost:8080/portalapp/header.do"; id="header"/> <bean:write filter="false" name="header"/> This seemed to work swimmingly, but upon closer scrutiny It generates lots of sessions in the central app, because every time I hit an app it calls header.do, footer.do, nav.do in the central app. So by hitting one page of any given app in the portal I generate 3 new sessions in the central app. For 20 seperate apps in the portal, this will obviously not scale well. My solution to this is to invalidate the session in the JSP becuase no session information is actually needed, everything is in the request. My question has two parts. First, is there a way to use struts without creating or maintaining any session info? Second, keeping in mind that I am already stuck with this architecture, does my solution of doing a Session.invalidate() sound reasonable? Thanks in advance. -- Joshua Cronemeyer
signature.asc
Description: This is a digitally signed message part
