[
https://issues.jboss.org/browse/SOLDER-1?page=com.atlassian.jira.plugin.s...
]
Pete Muir commented on SOLDER-1:
--------------------------------
No, the bean manager injected will be the one for the BDA in which solder is present. This
is completely correct if you think about it, resolvability follows accessibility, so the
only resolvable beans from solder will be the ones that are accessible (which if solder is
used as e.g. an installed library or perhaps an ear library is not much...).
I don't believe there is a good solution to this problem, short of finding a way to
find the BeanManager the client code (which you could do via a setter I guess).
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