[
https://issues.jboss.org/browse/SOLDER-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570164#comment-12570164
]
Dan Allen commented on SOLDER-1:
--------------------------------
Thanks for the explanation. Just gotta remember that now ;)
So perhaps the solution here is to expose a field into which the client code
can set the BeanManager (via Seam Config perhaps?). If that field is not set,
then we fallback to assuming the flat model. The only thing I'm unsure of is
whether what Seam Config pushes in will be any different. If it's not, can it
be assigned programmatically in a application startup method?
Sounds like this might be a documentation issue as much as a code change.
> 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
