Re: [seam-dev] API Support - JMS Observer Methods

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.