You have my question backwards. I am saying because of the fact that you can have any extension you want for struts (as set by the servlet mapping) then should you not have to hard code the extension (I used .do as an example) in the struts config forwards. This makes it more than just changing the web.xml from url-pattern *.do to *.yup, struts makes it so you have to change the web.xml AND the struts config filesssss. I do it with all the sssss at the end because I use modules so then I would have to change many struts config files if I want to change the extension. That is what I wanted to avoid (strictly for future possibilities).
-----Original Message----- From: Rohit Aeron [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 6:37 AM To: Struts Users Mailing List Subject: RE: Is this a bug with struts config file? I don't think you need to put .do. Actually in the web.xml file you have following code <servlet-mapping> <servlet-name>action</servlet-name> <url-pattern>*.do</url-pattern> </servlet-mapping> here you can configure as you want you can configure *.yup also & it works. Regards Rohit -----Original Message----- From: Aguirre Carlos Federico [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 5:28 AM To: [EMAIL PROTECTED] Subject: Re: Is this a bug with struts config file? Hi. the ".do" in forwards to actions is necessary because when you make a forward, the request is processed again by application server, if you not add .do in forwards to struts actions then the application server do not map the request to action servlet of struts. "Richard J. Duncan" <[EMAIL PROTECTED]> escribi� en el mensaje news:[EMAIL PROTECTED] > My experience is the same as yours. That while the ".do" can be omitted > in the action definition, it may not be omitted in the forward. FWIW, I > think this is proper behavior. Certainly if you html:link to the forward > your html pages will be do-less. Also, you can change to another scheme > (e.g., "/action/login") simply by modifying the structs-config. > > > > -----Original Message----- > From: Bailey, Shane C. [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2003 6:00 PM > To: [EMAIL PROTECTED] > Subject: Is this a bug with struts config file? > > > > Short version: > > I would think that I could do this then <forward name="home" > path="/home"/> > and Struts > > would know to add the .do for me. When a <html:link forward="home"> is > rendered it does not > > have the .do on it. I have to make it <forward name="home" > path="/home.do"/> > > > > Is that a bug? > > > > Since Struts determines extensions on the fly (at Servlet startup based > on > URL pattern in web.xml) > > it just seems defeating that you would have to hard code an extension > anywhere in the system. > > > > > > Longer version: > > In my crusade to wipe out all hard coded ".do" extensions in the app for > future upgradability > > (for instance all my links are like this <html:link action="/login"...> > instead of "login.do" > > > > I found that (unless something is not right) the global-forwardS don't > act > as I would expect. > > It implies in the struts config dtd that if contextRelative not true > then > the path is module relative. > > > > It seems minor but if I need to change the extension to ".go" or > something > else, > > say, because if a hacker doesn't know you are using Struts because the > extension is ".poo" then > > it may help the system. But in order to make the change I would have to > go > into all my many > > struts config files and globally replace ".do". Not too bad if I am > doing > it but when someone else > > in the group with less experience does it then it could be a pain. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *---------- This message and any attachment(s) is intended only for the use of the addressee(s) and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended addressee(s), you are hereby notified that any use, distribution, disclosure or copying of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachment(s) and notify the sender or Kanbay postmaster immediately. Any views expressed in this message are those of the individual sender and not of Kanbay. Although we have taken steps to ensure that this e-mail and any attachment(s) are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
