Merrill,
funny, that's exactly what I did and it worked just fine. Now however, my group and I have decided to go a different direction. Instead of each WAR we create having to have all the images/stylesheets/javascripts/shared JSPs we created a SharedContent WAR that is struts enabled. The only action is a forward like so:
<action path="/logout" forward="/WEB-INF/logout.jsp" />
in the webcontent area there is a logout.jsp with a logic:redirect to "logout.do"
The idea is that all future WARs will be built from a "BaseWAR" so that all WARs have a similar design.
in each WAR this IBM magical logout form will be provided and won't need to be changed:
<form method="post" action="ibm_security_logout" name="logout">
<input type="submit" name="logout" value="Logout">
<input type="hidden" name="logoutExitPage"
value="<SharedContent:path />/logout.jsp">
</form>
I created a custome tag SharedContent that ends up producing this:
https://some.server.com/context/root/SharedContent (This also allows me to do:
<img src="<SharedContent:path />/images/my_image.jpg">)
problem is struts seems to be doing something to the URL. When I click the logout button, I get a 404 and the URL reads:
https://my.server.com/context/root/MyApp/context/root/SharedContent is this a situation where I should have the logout form point to an action declared in the local struts config file which then redirects to a JSP in a completely different WAR?
curious,
Jason