Hi John, Yes, currently CDI doesn't call any event for beans, observer methods etc. added by you in ABD. We'll change this for CDI 1.1 I think
On 20 Feb 2011, at 14:18, John D. Ament wrote: > Pete, > > So I've been working on the approach you discussed on IRC. The code changes > do not work correctly when I look at the bean manager in > ProcessObserverMethod - it looks like this event gets called prior to ABD, so > my observer methods do not exist. However, it does look like it works > correctly when I process the bean manager that comes in during > AfterDeploymentValidation. I have to run a lot more testing, but it does > appear to work when I lazily create the beans. So, thanks for tips. > > John > > On Fri, Feb 18, 2011 at 6:19 AM, Pete Muir <[email protected]> wrote: > > On 18 Feb 2011, at 00:28, John Ament wrote: > > > For an overview of the original proposal, please review > > https://issues.jboss.org/browse/SEAMJMS-3 > > https://issues.jboss.org/browse/SEAMJMS-4 > > > > Why are we doing this? > > > > The issue raised recently on the list is that during AfterBeanDiscovery, > > there is no guarantee that beans are available. This conflicts with the > > Egress side of the feature where the full observer method must be created > > during ABD. As a result, we cannot guarantee that looking up beans will > > work (in fact, we can typically guarantee it won't work). Therefor, we can > > not support generic qualifiers on the destinations that are involved in the > > mapping, the extension needs to be able to resolve the destination manually. > > John can you explain in more detail why you need to look up beans here? > > This restriction has generally not been a problem for implementing such > extensions, so I'm curious why it is here. > _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
