I realize that FacesContext is not available on a Seam remoting call because the request does not go through the JSF lifecycle. However, since the FacesContext is null, the Spring beans EL integration also goes out the window. Instead, Seam uses an internal UnifiedELValueBinding that is unaware of any custom JSF variable resolvers ;( Would it be possible to add a configuration in Seam to add variable resolvers when the FacesContext is not available? For those of us using Spring beans, they become pretty important during a remoting call. Naturally, it would always be possible to drop back to using lookups for the Spring application context, but that would be a step backwards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029195#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...