Search:

I agree, and it sounds like you're on the path to the most flexible solution that would allow for different use cases to handle errors in different ways. I know in our envirnonment, I could make use...

Hey Mark -

I'm beginning to use 1.0.3 and have not yet looked at the 2.0 milestone, yet. I have this same issue where I'm using a message driven channel adapter, and am simply routing it out to...

I agree, this is a huge pain. I'm not a Maven user, but use Ivy instead. Ideally, Spring's own Ivy repository would include Spring Modules (It amazes me that they don't even publish to their own...

I found an alternative. Sharing in case it could help someone in a similar situation.

Even though it's not as clean as I would have liked, it allows me to leave my pages and links as .jsp, and...

I too experience the endless loop if I have my DispatcherServlet handle all *.jsp requests. I've stepped through it and see it get all the way to the rd.include or rd.forward call on the...

I finally realized that the additional / was coming from my ViewResolver which I had set to have a prefix of "/".

I went back and stepped through the code in Tomcat and it was happening there,...

I have a Spring MVC application which was working perfectly in Tomcat. I need to deploy it to Websphere in our production environment. I have copied all of the code and config over, and now in...

For those interested, I found there's a much easier way than what I had implemented in my controller previously. I stumbled onto this, actually, just by trial and error. The following accomplishes...

Possibly there are other ways, but this finally worked:

Override the referenceData method in my controller, so that I can have access to the Errors object in the controller after it's been...

Unfortunately, I've already tried that. It doesn't seem to pick up all errors. The bind tag is binding to a top level object and only seems to pick up errors which are bound to that object, and...

I know that I can print all errors for my form submission using <form:errors path="*" />. but I would like to create an error header 'Error Messages', and then have my individual error messages...