[
https://issues.jboss.org/browse/SOLDER-1?page=com.atlassian.jira.plugin.s...
]
Dan Allen commented on SOLDER-1:
--------------------------------
I'm having trouble understanding the problem. The producers for ELResolver, ELContext
and Expressions are all dependent-scoped. They are presumably used to inject into an
injection point in the user's application. I would assume, then, that the BeanManager
that is injected into the producer is going to be the one corresponding to the injection
point, which would be the right one.
If my explanation is incorrect, can you please suggest where we should be looking to solve
this problem?
ELResolver assumes flat deployment structure
--------------------------------------------
Key: SOLDER-1
URL:
https://issues.jboss.org/browse/SOLDER-1
Project: Seam Solder
Issue Type: Bug
Reporter: Pete Muir
Labels: el, scoping
Fix For: 1.0.0.Beta2
It adds the ELResolver belonging to the BeanManager of the seam-solder.jar module, when
in fact the user will want the ELResolver for the bean manager from their module/app.
public class ELResolverProducer
{
@Produces
@Composite
public ELResolver getELResolver(@Resolver Instance<ELResolver> resolvers,
BeanManager beanManager)
{
// Create the default el resolvers
CompositeELResolver compositeResolver = new CompositeELResolver();
compositeResolver.add(beanManager.getELResolver());
...
}
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira