Good news, thanks for the following up.
Mike
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029395#4029395
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029395
___
jboss-use
If the Spring listener is configured above the Seam listener in web.xml, then
Seam complains loudly that a component is being accessed outside the context of
a web application when adding the SpringComponent.
java.lang.IllegalStateException: Attempted to invoke a Seam component outside
the cont
I created an issue to work on better spring EL integration if you want to track
it: JBSEAM-1074
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029358#4029358
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029358
__
Thanks for working through this and providing a solution. What "strange
errors" were you getting when you bean was not marked as lazy?
Mike
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029348#4029348
Reply to the post :
http://www.jboss.com/index.html?mo
Oh yeah! I finally figured out a way to do away with the need for the
delegating variable resolver all together, which in my mind really feels like
the right solution to this problem! I am now using to expose
my Spring bean as a native Seam component instance rather than relying on the
varia
