- 
        1. Re: MBean to be a topic subscriber, how?alanc_yang Mar 31, 2004 9:30 PM (in response to alanc_yang)add something similar to the depolyment descriptor. 
 <resource-ref>
 <res-ref-name>jms/QCF</res-ref-name>
 <res-type>javax.jms.ConnectionFactory</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
- 
        2. Re: MBean to be a topic subscriber, how?alanc_yang Mar 31, 2004 10:27 PM (in response to alanc_yang)Actually, it still not quite right. If I restart the server, the error would occurred. But if I re-deploy the MBean after the server started, the problem would go away. What could be the issue? 
- 
        3. Re: MBean to be a topic subscriber, how?adrian.brock Apr 1, 2004 6:53 AM (in response to alanc_yang)Have you modified jboss's jndi.properties? 
 Show the enumeration of the listBindings("") and the context's environment.
 Regards,
 Adrian
- 
        4. Re: MBean to be a topic subscriber, how?alanc_yang Apr 1, 2004 10:13 AM (in response to alanc_yang)This is the jndi.properties file under /server/default/conf for jboss server that started. Really not sure how to modify for the ConnectionFactory. 
 java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
 java.naming.provider.url=jnp://localhost:1099
 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
 Also, the enumeration of listbinding, you mean to view from JMX console? Thank you and sorry about the naiveness.
 Alan
- 
        5. 3846641mring33 Apr 1, 2004 1:58 PM (in response to alanc_yang)I wonder if this is an initialization timing problem? Maybe your MBean is being initialized before the ConnectionFactory is ready. Try adding a tag to your jboss-specific xml file for the MBean. 
 Something like this (Sorry, I wasn't sure of the right path/name for the ConnectionFactory, but maybe a dependency on the JMSProviderLoader is good enough):<mbean code="foo.MyMBean" name="fooApp:service=MyMBean"> <depends>jboss.mq:service=JMSProviderLoader</depends> </mbean> 
 Good luck!
 -Matthew S. Ring
 
     
    