The standard java @Valid annotation doesn’t support groups. However, Spring now includes an @Validated annotation which does the same job as @Valid, but allows you to specify which groups to use in the validation: @ModelAttribute(“myCandidate”) @Validated(UpdateGroup.class) Candidate myCandidate Note that this annotation is only available in Spring 3.1 and newer.
HttpRequestBase is a class and ReSharper sees it as an actual Class, nothing more (theoretically, it can be null). So it does not analyze the usage of this specific Class. In reality, I think that Request.Url will never be null, so just ignore ReSharper in this case.
if the form has these buttons specified: input type=”submit” class=”button” name=”save” value=”Save” input type=”submit” class=”button” name=”delete” value=”Delete” input type=”submit” class=”button” name=”cancel” value=”Cancel” you may direct to different url request according to button pressed with one controller. for cancel button, @RequestMapping(params = “cancel”, method = RequestMethod.POST) public String cancelUpdateUser(HttpServletRequest request) { return “redirect:/users.html”; } what request … Read more
You could use the following if you have access to the HttpContext: var urlHelper = new UrlHelper(HttpContext.Current.Request.RequestContext);
If you want to cache an action, based on all the query parameters (or say on nearly all of them), you can do: caches_action :my_action, :cache_path => Proc.new { |c| c.params } Or, maybe you want all but some params that you just use for Analytics (but that have no bearing on the records you’re … Read more
Controllers are typically used to be bound with a view. Controllers manage a view’s life cycle, and should be thought of as View Controllers. A new controller will be created for each instance of a view, meaning that if you navigate away from a certain view, and then back again – or if you have … Read more
a couple of ways I have done this in the past put the data in hidden fields, access the data in js/coffee # single value <%= hidden_field_tag “foo_name”, @foo.name, { :id => “foo-name” } %> $(‘#foo-name’).val(); # when the ‘value’ has multiple attributes <%= hidden_field_tag “foo”, @foo.id, { :id => “foo”, “data-first-name” => @foo.first_name, “data-last-name” … Read more
Moq and other similar mocking frameworks can only mock interfaces, abstract methods/properties (on abstract classes) or virtual methods/properties on concrete classes. This is because it generates a proxy that will implement the interface or create a derived class that overrides those overrideable methods in order to intercept calls.
I had the same problem. solved it like this: return new ModelAndView(“redirect:/user/list?success=true”); And then my controller method look like this: public ModelMap list(@RequestParam(required=false) boolean success) { ModelMap mm = new ModelMap(); mm.put(SEARCH_MODEL_KEY, campaignService.listAllCampaigns()); if(success) mm.put(“successMessageKey”, “campaign.form.msg.success”); return mm; } Works perfectly unless you want to send simple data, not collections let’s say. Then you’d have … Read more
Add the following dependencies <dependency> <groupId>org.codehaus.jackson</groupId> <artifactId>jackson-mapper-asl</artifactId> <version>1.9.7</version> </dependency> <dependency> <groupId>org.codehaus.jackson</groupId> <artifactId>jackson-core-asl</artifactId> <version>1.9.7</version> </dependency> Modify request as follows $.ajax({ url:urlName, type:”POST”, contentType: “application/json; charset=utf-8”, data: jsonString, //Stringified Json Object async: false, //Cross-domain requests and dataType: “jsonp” requests do not support synchronous operation cache: false, //This will force requested pages not to be cached by the … Read more