Both approaches work fine, in fact we had a discussion about using Both. Actually the BASE tag just works fine, the same view may be generated by
Any action and the JSP URL will get masked by the one from where The jsp is called(forwarded action). Base tag supports all the other Reference links(like stylesheets,images etc etc) on the page, and it is already available (we don't Need to re-desing/re-write anything). Anand -----Original Message----- From: Dylan MacDonald [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: base href (html:base) tag Hi - I'm a bit of a newbie to Struts so I hope you can bear with me. I'm one of several developers working on a struts framework Registration project for my company. We are currently having an internal debate as to how to set up application contexts and asset pathing in our JSP pages for this and future projects we are slated to build. The Java Architect on the project believes we should use the <html:base/> tag in our JSPs. That way we can set the context (or pathing) via the taglib. This would help for transferring files between our Dev and Production environments, for example. A few of the web developers believe that we should set a J2EE directive which maps all requests to the application context we set. That way, we can set the pathing to be whatever we want without being constrained by what the Base Href is. By using <html:base/>, I assume that we will be adding a BASE HREF tag to the top of every JSP page. I think this is odd. I never set a BASE HREF tag unless I want to view the page completely out of context (like on my desktop). Moreover, who really uses BASE HREF on every JSP page? I almost never see it in the source code of sites I visit. It just strikes me as odd and an unusual practice. Any thoughts? Thanks, Dylan MacDonald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
