Home/ Questions/Q 6739221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T11:27:41+00:00

Using Spring/SpringMVC 3.0.5 I’ve defined a method in my controller like this: @RequestMapping(params =

  • 0

Using Spring/SpringMVC 3.0.5 I’ve defined a method in my controller like this:

@RequestMapping(params = { "save","!delete" }, method = RequestMethod.POST)
public ModelAndView saveFoo(...
    @ModelAttribute("vo") @Valid DescriptionBuilderVO vo, BindingResult result) {
    ...
    result.rejectValue("foo.sequenceNumber", "foo.builder", new Object[]{vo.getFoo().getSequenceNumber()}, "Sequence Number too high");    vo.getFoo().setSequenceNumber(originalNumber);
    return new ModelAndView(WebConstants.VIEW_BUILDER, "vo", vo);

Notice that I’m attempting to set a value in the VO object inside the controller. The funny thing is that if I do this with @ModelAttribute the new value doesn’t show up. If I remove @ModelAttribute from the method contract, the new value appears exactly as you would think. The problem comes when there are errors, the only way to get the errors is to have the @ModelAttribute in the contract.

BTW my HTML looks like:

HTML

<form:input path="foo.sequenceNumber" id="sequenceNumber" size="4" maxlength="4"/>
<form:errors path="foo.sequenceNumber" cssClass="ui-state-error" />

foo.sequenceNumber = the value the user typed in; when I use @ModelAttribute
foo.sequenceNumber = the value I set in the controller; but I lose any errors

It seems to me that SpringMVC is putting the ModelAttribute VO into a “special” place and passing it back to the jsp but not in an obvious location. Does anyone know how I can get at the VO object in this situation?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve tried many different things including the reordering the Valid and ModelAttribute annotations and it doesn’t seem to make a difference.

    In reading the documentation suggested by Pat in the comments it does refer to a special context where the VO is stored. Anyway, if you’re trying anything similar to this I suggest you go about it in a different way perhaps building a completely new VO and passing it back to the view, which is what I did.

    • 0