You can do a compile time include instead of a run-time include.
Tim:
We wanted to avoid that because we're including quite a lot of stuff, and it is being included on every page. Naively, I felt that duplicating all that header and footer logic and HTML in every generated servlet would be unwise. But I'm very new to this, so I may be off base.
The general setup is that we have the typical standardized header and footer, and some standardized, but conditional, navigation stuff. This is all part of two include files called, aptly, "Header.jsp" and "Footer.jsp". These files are included on nearly every page, so that the page itself only needs to define its unique content. Our header performs the requisite check that the user is authenticated, and attempts to redirect to the login page if not. For some reason it worked fine until recently, perhaps coinciding with our switch to the latest stable tomcat.
It seems like we need our authentication check and redirect (or forward) on the content page itself and not in an include, so Muffi created a taglib to encapsulate this check and that seems to be working. Is this a typical solution? It seems like a frustrating restriction to prevent redirects or forwards in includes. Does anybody know the reason for this limitation? Does anybody have a better way to accomplish what I'm describing?
Thanks for all your help so far!
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
