Url navigation

[too_many_details]

Hi,

I would like to know if there is a better way to to redirects in my Spring app.

At the moment, for example, my change password page could lead to either the error page or the main app page. Returning a new ModelAndView object of the relevant view works but does not update the browser url.

To get round this I use response.sendredirect():

...
       response.sendRedirect(request.getContextPath()+"/secure/main.htm");
        return null;

However, I now have to keep the url in the controller upto date with the mappings in the servlet xml file:

	<bean name="/secure/main.htm" class="com.ifst.web.controllers.MainPageController"/>

Thanks

Rakesh

[falaserioaih]

Have you tried this?

return new RedirectView(....

[too_many_details]

Hi,

thanks for the tip. I got it working using this:

        RedirectView rv = new RedirectView("/secure/main.htm",true);
        return new ModelAndView(rv);

Its a bit cleaner but still has the url hard coded but i guess there's not much that can be done about that.

Thanks for your time

Rakesh

[too_many_details]

Hi,

as a follow on to my original question, how do i accomplish the same thing when there is also some data i wish to pass to the next view?

This is how it currently works, an error condition in the controller looks like this:

        } catch (InvalidLogonException e) {
            return errorPageRedirect(e);
.
.
.
    private ModelAndView errorPageRedirect(Exception e) {
        logger.debug(e.getMessage());

        ModelAndView mav = new ModelAndView("login_failure");
        mav.addObject("reason", e.getMessage());

        return mav;
    }

so, like before, the browser url does not update. Can i get round this??

Thanks

Rakesh

[falaserioaih]

I think you could make this way:

        RedirectView rv = new RedirectView("/secure/main.htm",true);

        Map myModel = new HashMap();
        myModel.put("reason", e.getMessage());

        return new ModelAndView(rv, "model", myModel);

[Colin Yates]

From an "point on concerns" point of view, I think it is "leakage" to have your controller determine whether to forward or redirect. It is much better (in my very humble, but overly opinionated opinion) for your controller to just return a model and view based on a view name, and then the definition of that view is either redirect or forward etc.