<div>All,</div><div><br></div><div>I&#39;ve run into an issue that I haven&#39;t been able to resolve. I am collecting producers during ProcessProducer and I&#39;d like to be able to invoke them during AfterBeanDiscovery to operate on the produces objects. When I run the application with Arquillian the beans can be looked up successfully. When the application runs as a web app they are not.</div>


<div><br></div><div>The sample app is producer-test on this branch of seam-jms: <a href="https://github.com/jganoff/jms/tree/producer-test/producer-test">https://github.com/jganoff/jms/tree/producer-test/producer-test</a></div>
<div><br></div><div>The relevant code is here: <a href="https://github.com/jganoff/jms/blob/producer-test/producer-test/src/main/java/org/jboss/seam/jms/producertest/TestExtension.java">https://github.com/jganoff/jms/blob/producer-test/producer-test/src/main/java/org/jboss/seam/jms/producertest/TestExtension.java</a></div>
<div>

<br></div><div>Anyone have any ideas?</div><div><br></div><div>Follow up question: Is this a decent way for users to configure JMS routing information (send CDI event X to JMS destination Y, etc)? The original idea was to allow users to annotate methods with  @RoutingConfig and what they returned would be registered as a route. The producer idea seemed like a better fit though.</div>

<div><br>-- <br>Jordan Ganoff<br>
</div>