[ http://jira.jboss.com/jira/browse/JBSEAM-1074?page=comments#action_12356697 ] Michael Youngstrom commented on JBSEAM-1074: -------------------------------------------- Working on this issue I created a SpringELResolver Component and on startup I added as an ELResolver to EL.EL_RESOLVER. However, it appears to be ignored for regular web requests. I'm not exactly sure how all the EL stuff is set up in Seam but it appears that even with a SpringELResolver the user will still need to specify the Spring DelegatingVariableResolver in the faces-config. Is that true? Or is there some way I'm not seeing that I can set up the SpringELResolver to work for both faces requests and non faces requests? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1074?page=comments#action_12356708 ] Michael Youngstrom commented on JBSEAM-1074: -------------------------------------------- Ok, the goal of the issue is to make Spring beans available to expressions of offline requests. So to be clear this is what I did and what the user will be expected to do: 1. I Created a SpringELResolver made it a Seam component and add it to the EL.EL_RESOLVER CompositeResolver on startup so now Spring beans can be found using expressions when not in a faces request. 2. If the user is using JSF 1.1 they will still have to specify the spring DelegatingVariableResolver in their faces-config so that spring beans will be found during FacesRequests. 3. If the user is using JSF 1.2 they can either specify the spring DelegatingVariableResolver in their faces-config or they could optionally specify the SpringElResolver seam provides but either way the user will have to specify something in the faces-config. So #1 does not eliminate the user having to do 2 or 3 correct? Mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1074?page=comments#action_12356711 ] Gavin King commented on JBSEAM-1074: ------------------------------------ eg, it would be nice if we could arrange it so that Seam would always use its own EL context, but then somehow delegate to the JSF context. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1074?page=all ] Michael Youngstrom updated JBSEAM-1074: --------------------------------------- Summary: Provide EL Integration for Spring Beans when not in faces request (was: Look into providing better EL Integration for Spring Beans) Affects: [Interactive Demo/Tutorial] (was: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Compatibility/Configuration]) updated affects and subject -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira