Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7541663
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T07:57:09+00:00 2026-05-30T07:57:09+00:00

While working with Spring 3.x and and JSF 2.x, we can register the Spring

  • 0

While working with Spring 3.x and and JSF 2.x, we can register the Spring Beans EL resolver for JSF in the faces-config.xml as:

<application>
    <el-resolver>org.springframework.web.jsf.el.SpringBeanFacesELResolver</el-resolver>
</application>

Is there a way we can do this programmatically and get rid of faces-config.xml?

Edit: 02/27/2012
I found a way to get this working. Not quite sure yet but I’m still reviewing my solution. Here’s is how I got it working.
1.Write a Java Servlet and implement its init() method which contains the code to register ELResolver i.e.

public final class ELResolverInitializerServlet extends HttpServlet {

private static final Logger LOGGER = Logger.getLogger(ELResolverInitializerServlet.class.getName());

private static final long serialVersionUID = 1L;

/**
 * @see HttpServlet#HttpServlet()
 */
public ELResolverInitializerServlet() {
    super();
}

/**
 * @see Servlet#init(ServletConfig)
 */
public void init(ServletConfig config) throws ServletException {
    FacesContext context = FacesContext.getCurrentInstance();
    LOGGER.info("::::::::::::::::::: Faces context: " + context);
    context.getApplication().addELResolver(new SpringBeanFacesELResolver());

}

}

2.Register this servlet using Spring’s bootstrapper org.springframework.web.WebApplicationInitializer i.e.

public class AppInitializer implements WebApplicationInitializer {

private static final Logger LOGGER = Logger.getLogger(AppInitializer.class
        .getName());

@Override
public void onStartup(ServletContext servletContext) throws ServletException {
    LOGGER.info("Bootstraping Spring...");
            ...

    ServletRegistration.Dynamic elResolverInitializer = servletContext
            .addServlet("elResolverInit",
                    new ELResolverInitializerServlet());
    elResolverInitializer.setLoadOnStartup(2);
            ...
}

}

With this configuration, Spring bootstrapper registers the servlet as a loadOnStartup servlet. This servlet is loaded after the JSF’s FacesContext is created. Then it adds the ELResolver to the JSF’s context which is available for the application after the application starts up.

Any thoughts / reviews are welcome.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T07:57:11+00:00Added an answer on May 30, 2026 at 7:57 am

    Take a look at addELResolver method in Application class.
    Something like:

    FacesContext.getCurrentInstance().getApplication().addELResolver(myResolver);
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm working on a Spring application that simply searches a set of data for
I have a working Spring MVC application(doing everything I wanted when deployed to jboss)
while working on an application that requires converting strings to long numbers the atol()
I have been working with Spring for a while now to realize that not
I have a working web service client based on Spring, defined as: <bean id=myService
I'm new to working with XML, and I've encountered a weird problem while trying
Working with spring, below, the code of applicationContext-service.xml: <bean id=mediaObjectService class=path.MediaObjectServiceImpl> <property name=mediaObjectDao >
a little background here.I've been working with spring+hibernate(JPA+Session)+maven for while now.I'm used to Hibernate
While working in a Java app, I recently needed to assemble a comma-delimited list
While working between a Windows MySQL server and a Debian MySQL server, I noticed

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.