Done. You can also add comments directly to the page.
-T. On 3/28/07, doktora <[EMAIL PROTECTED]> wrote:
I think the fact that you cannot change the location of struts.xml should be put in here: http://struts.apache.org/2.x/docs/struts-1-solutions.html This will help out a lot of people who do not expect s2 to have this different behaviour. I failed to find this documented anywhere which cost me quite a bit of time and frustration with s2 because I couldn't even jumpstart it. Ted Husted-4 wrote: > > Struts 2 uses a different approach to loading the configuration. The > initial struts.xml is loaded from the root of the classpath. The > easiest way to set that up is to put the struts.xml under the classes > folder. The "boostrap" struts.xml can then load whatever other > struts.xml's you would like using the include element. > > HTH, Ted > <http://www.husted.com/ted/blog/> > > > On 3/27/07, doktora <[EMAIL PROTECTED]> wrote: >> >> Why is it that putting this in the FilterDispatcher <filter> section in >> web.xml breaks Sturts2: >> >> <init-param> >> <param-name>config</param-name> >> <param-value>/WEB-INF/struts.xml</param-value> >> </init-param> >> >> It looks to me as if this makes S2 confused about the whereabouts of its >> other struts-default.xml, etc. files. >> >> >> doktora >> >> >> Ted Husted-4 wrote: >> > >> > Put a stub struts.xml on the classpath that loads your working >> > configuration from another location. If the stub is under classes and >> > the one you want is under WEB-INF, try >> > >> > <struts> >> > <include file="..\struts.xml"/> >> > </struts> >> > >> > -HTH, Ted >> > <http://www.husted.com/ted/blog/> >> > >> > On 3/19/07, Bartek <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi >> >> >> >> I have to face up the following issue. My location of struts.xml >> shoudl >> >> be >> >> WEB-INF directory, not WEB-INF/classes. >> >> What is the easiest way to achieve this?? I tried several different >> >> config >> >> locations (e.g. WEB-INF/struts.xml) for >> StrutsXmlConfigurationProvider, >> >> none >> >> of them worked. Creating custom configuration provider might help, but >> it >> >> is >> >> pojo by default , protocol independant and therefore without any >> >> ServletContext access - what is a pain in this case. >> >> >> >> Cheers >> >> bartek
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
