maven upgrading
Hello, I have recently moved over to maven, so this may be a bit of a dumb question, when I change my version to 2.3.15 it wants to add to the build all previous jar versions? /target/events/WEB-INF/lib/struts2-core-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-core-2.3.14.jar /target/events/WEB-INF/lib/struts2-core-2.3.15.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.15.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.15.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.15.jar /target/events/WEB-INF/lib/xwork-core-2.3.14.2.jar /target/events/WEB-INF/lib/xwork-core-2.3.14.jar /target/events/WEB-INF/lib/xwork-core-2.3.15.jar Is there something I have to do to only use the latest version? org.apache.struts.version2.3.15/org.apache.struts.version dependency groupIdorg.apache.struts/groupId artifactIdstruts2-core/artifactId version${org.apache.struts.version}/version exclusions exclusion artifactIdasm-commons/artifactId groupIdasm/groupId /exclusion exclusion artifactIdasm/artifactId groupIdasm/groupId /exclusion exclusion artifactIdjavassist/artifactId groupIdjavassist/groupId /exclusion /exclusions /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-tiles-plugin/artifactId version${org.apache.struts.version}/version /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-spring-plugin/artifactId version${org.apache.struts.version}/version /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-javatemplates-plugin/artifactId version${org.apache.struts.version}/version /dependency Cheers Greg
ServletResponseAware - request can be null?
Hi, I am implementing the ServletResponseAware interface and found out that sometimes the HttpServletResponse is null when I execute() the action. ServletConfigInterceptor is definitely executed before. Actually often the HttpServletResponse is not null and my code seems to work. Not sure if I should worry about that or not. Any ideas under which conditions the HttpServletResponse can be null (in a Struts 2 application, recent version)? Thanks! Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: maven upgrading
Did you do an mvn clean? Dave On Jul 5, 2013 4:48 AM, Greg Huber gregh3...@gmail.com wrote: Hello, I have recently moved over to maven, so this may be a bit of a dumb question, when I change my version to 2.3.15 it wants to add to the build all previous jar versions? /target/events/WEB-INF/lib/struts2-core-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-core-2.3.14.jar /target/events/WEB-INF/lib/struts2-core-2.3.15.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-javatemplates-plugin-2.3.15.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-spring-plugin-2.3.15.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.14.2.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.14.jar /target/events/WEB-INF/lib/struts2-tiles-plugin-2.3.15.jar /target/events/WEB-INF/lib/xwork-core-2.3.14.2.jar /target/events/WEB-INF/lib/xwork-core-2.3.14.jar /target/events/WEB-INF/lib/xwork-core-2.3.15.jar Is there something I have to do to only use the latest version? org.apache.struts.version2.3.15/org.apache.struts.version dependency groupIdorg.apache.struts/groupId artifactIdstruts2-core/artifactId version${org.apache.struts.version}/version exclusions exclusion artifactIdasm-commons/artifactId groupIdasm/groupId /exclusion exclusion artifactIdasm/artifactId groupIdasm/groupId /exclusion exclusion artifactIdjavassist/artifactId groupIdjavassist/groupId /exclusion /exclusions /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-tiles-plugin/artifactId version${org.apache.struts.version}/version /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-spring-plugin/artifactId version${org.apache.struts.version}/version /dependency dependency groupIdorg.apache.struts/groupId artifactIdstruts2-javatemplates-plugin/artifactId version${org.apache.struts.version}/version /dependency Cheers Greg
Re: Possible client side validation bug in Struts 2.3.15
Now I managed to create a minimal example that reproduces the error (the previous example I was trying was too minimal :) https://github.com/bklava/struts In the example, in the index action/page, there are 2 forms: the difference is that the form 1 submits to the action without setting a method (then calling the default execute() method), while the form 2 submits to the same action but calling a specific method. The validator is set annotating the field setter method, so it should be available either to the default execute method and to the non-default method. This is exactly the behaviour obtained when using Struts 2.3.14.3. After switching to Struts 2.3.15, the form 2 validation is not executed at all. As far as I can tell, this difference is due to changes made in org.apache.struts2.components.Form.getValidators(String name) If you need any further info, just ask. Tnx! Bruno On Thu, Jul 4, 2013 at 4:25 PM, Bruno Klava bkl...@gmail.com wrote: Hi Maurizio, is was generating a minimal example but could not reproduce the bug in it. It must be something else, maybe a customized template/component. tnx anyway ;) Bruno On Wed, Jul 3, 2013 at 4:20 PM, Maurizio Cucchiara mcucchi...@apache.orgwrote: Hi Bruno, could you provide a code sample? Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara Maurizio Cucchiara On 3 July 2013 21:09, Bruno Klava bkl...@gmail.com wrote: Hi folks, after upgrading Struts from 2.3.14.3 to 2.3.15 my client side form validation stopped working. More specifically, the code to validate requiredstring is not being generated in the validateForm_xx() functions. Is anybody having the same issue? Tnx in advance, Bruno -- Bruno Klava -- Bruno Klava