[
https://issues.jboss.org/browse/SOLDER-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570172#comment-12570172
]
Pete Muir commented on SOLDER-1:
--------------------------------
BTW that is a hypothetical solution, not one that is implementable today.
Can you file a CDI issue for this?
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
