Please see the post which i have done in the spring web forum.
As per me , it may be bug inside the spring 3.0…..

http://forum.springsource.org/showthread.php?t=83605

if you are not able to reach this post , then search for "RequestMaping calling two times for one submit"

Please reply back

Thanks
Rahul

I downloaded "spring-framework-2.5.6.SEC01" but I can't seemed to find an example of a Spring Mvc Annotations example in the "C:\Download\Spring25\temp\spring-framework-2.5.6.SEC01\samples" directory. Does anybody know of a good Spring MVC Annotations example I can download from the web or from the spring web site.

Any help or hint would be greatly appreciated it.

Yours,

Frustrated.

Does anybody know where to get the full code download for this excellent example?

Maybe a better example about my concern is a web site with a common HTML component across all pages, perhaps a menu or a dynamic header. Using @MVC, every single @RequestMapping method will have to populate the model with the data for the common components. You could extract this into some external method, but there is no way around the fact that every single @RequestMapping method will have to make this call.

Does no one else see the inability to do OO inheritance as a problem? To me, the loss of inheritance is a hell of a price to pay just to simplify XML configuration. Inheritance is one of the main features of an OO language, without OO is this even Java anymore?

I suppose one approach would be to create methods in a base controller tagged with @RequestMapping for GET and POST like this:

public abstract class BaseSecurityController {
@RequestMapping(method=RequestMethod.GET)
public String checkSecurity(HttpServletRequest req) {
if (!securityService.checkAuth(req)) {
return "loginView";
}
handleGet(req);
}
public abstract void handleGet(HttpServletRequest req);
}

@Controller
public class SomePageController extends BaseSecureController {
@Override
public String handleGet(HttpServletRequest req) {
//….
return "view";
}
}

But that removes a lot of the flexibility of the method signatures and @RequestMapping. Is there a better technique?

There is an SPR mentioned in the posting that was resolved in Spring 2.5.3. Have a look at using ControllerClassNameHandlerMapping instead of SimpleUrlHandlerMapping. The approach works with both @Controller and with XML-based controllers.

For more details see this infoq article:
http://www.infoq.com/articles/spring-2.5-ii-spring-mvc

<bean id="ltbController" class="com.lastminute.lfe.dashboard.web.LtbController">
<constructor-arg ref="jdbcSubagentManager"/>
</bean>