[seam-issues] [JBoss JIRA] Updated: (SOLDER-1) ELResolver assumes flat deployment structure
[
https://issues.jboss.org/browse/SOLDER-1?page=com.atlassian.jira.plugin.s...
]
Dan Allen updated SOLDER-1:
---------------------------
Labels: el scoping (was: )
Description:
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());
...
}
}
was:It adds the ELResolver from the BeanManager for weld-extensions.jar, when the user
will want the ELResolver for the bean manager from their module/app.
Complexity: Low
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