Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0
-
None
-
Win2K and Linux on intel, Sun JDK1.4.2_04, Sun Filesystem JNDI provider 1.2, ActiveMQ 1.0-M1
Description
I was trying to learn how to use ActiveMQ.
I try using Sun's Filesystem JNDI provider instead of using say RMI registry or some other JNDI provider that comes with app servers.
The problem I am having is, when I bind an ActiveMQTopic to Sun's filesystem provider, what I looked-up from the other JVM is a javax.naming.Reference object instead of what I was expecting i.e. ActiveMQTopic objects.
Looking into the .bindings used by the filesystem JNDI reveals what I think is the explaination:
#This file is used by the JNDI FSContext.
#Thu Jun 03 14:05:58 PDT 2004
FOO/RefAddr/0/Encoding=String
FOO/RefAddr/0/Content=FOO
FOO/FactoryName=com.spirit.core.util.resolver.JNDIResolver
FOO/ClassName=org.codehaus.activemq.message.ActiveMQTopic
FOO/RefAddr/0/Type=physicalName
Is it intentional that the FactoryName is set to com.spirit.core.util.resolver.JNDIResolver?
Isn't spirit soft commercial software?
Looking into the code, it seems to be coming from org.codehaus.activemq.jndi.JNDIReferenceFactory.createReference().
Well, hope to hear from you soon about this.
Many thanks in advance.