Why isn't configuration being activated when an error page is rendered?

[Dave Alvarado]

Hi,

I'm using Spring 3.0. I create this application scope bean in my configuration file ...

@Configuration
public class Web implements ServletContextAware {
...	
	@Bean(name = "bookNowObject")
	public SearchResultHotels getBookNowLinkObject() { 
        SearchResultHotels linkObject = new SearchResultHotels();
        linkObject.setName("Book a Room");
        linkObject.setUrl("http://...");
        servletContext.setAttribute("bookNowObject", linkObject);
        return linkObject;
	}	// getBookNowLinkObject

However, if the first page that I visit is my /error-pages/500.jsp page, the "bookNowObject", referenced on that error page is null. If I visit the home page of my application, and then go back and visit the error page, the bookNowObject does get defined. Why does the configuration not get activated when the first page I visit is my error page?

Thanks, - Dave

[Mark Spritzler]

Why are you going directly to your error page first??? I mean wouldn't any user go to an actual page, then something else that they might do cause an error?

Mark

[Dave Alvarado]

I am visiting another page first that results in being redirected to the error page through the JSP

<%@ page errorPage="/WEB-INF/error-pages/500.jsp" %>

directive. - Dave