Re: strust2: filter-mapping best practice - /*

hi, you can always use extensionless actions, as long as they're under some directory. example: struts2 /action/* struts2 /struts/* in the case, static content (HTML, CSS, JS, etc.) located outside /action is served directly by the web server/jsp

Re: Struts mapping

i guess you mean "the web server/jsp container ignores the welcome-file-list", as struts2 takes over everything with /*. the workaround may be to either: - if you're using actions without extension: change struts2 filter mapping from /* to /actions/* and have actions under /actions - if you're usi

Re: avoiding unwanted value stack manipulation

tor.html > [2] - > http://struts.apache.org/2.1.6/struts2-core/apidocs/com/opensymphony/xwork2/interceptor/ParameterNameAware.html > > On Mon, Mar 23, 2009 at 1:53 PM, José Santos > wrote: > > hi, > > > > what's the recommended design for avoiding fields of D

avoiding unwanted value stack manipulation

hi, what's the recommended design for avoiding fields of DTOs in the value stack being updated through (HTML) DOM manipulation? consider a typical edit page containing a form with some fields. this page is a visual representation of a DTO we are about to update. the DTO is set in the action - it

[struts 2.1.6] ShortRangeFieldValidator and LongRangeFieldValidator

in struts 2.1.6/xwork 2.1.2, annotations @ShortRangeFieldValidator and @LongRangeFieldValidator do not exist in com.opensymphony.xwork2. validator.annotations. any way to apply such validations using annotations? santos.

@{Short,Long}RangeFieldValidator

in struts 2.1.6/xwork 2.1.2, annotations @ShortRangeFieldValidator and @LongRangeFieldValidator do not exist in com.opensymphony.xwork2.validator.annotations. any way to apply such validations using annotations? santos.