Hello.
I have a component which connects to an OpenJMS server (which is running in
phoenix). If I host the component in fortress, I can connect fine. If I
host it in merlin, I constantly get:
Cause: javax.naming.NoInitialContextException
Message: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory
The component is configured via this snippet:
<target path="/publisher">
<configuration>
<jndi>
<parameter name="java.naming.factory.initial"
value="org.exolab.jms.jndi.InitialContextFactory"/>
<parameter name="java.naming.provider.url"
value="rmi://localhost:1099"/>
</jndi>
<message type="xml"/>
<topicFactory>JmsTopicConnectionFactory</topicFactory>
<queueFactory>JmsQueueConnectionFactory</queueFactory>
<destination name="topic1" type="topic"/>
</configuration>
</target>
Basically, it loads the <jndi> parameters into a java.utils.Properties
object and establishes the InitialContext as follows:
Parameters jndi =
Parameters.fromConfiguration(conf.getChild("jndi",true));
m_environment = Parameters.toProperties(jndi);
...
InitialContext context = new InitialContext(m_environment);
The block.xml file has the following in the <engine> specification:
<resource id="openjms:openjms-client" version="0.7.5"/>
<resource id="openjms:openjms-rmi" version="0.7.5"/>
<resource id="openjms:exolabcore" version="0.3.5"/>
So the openjms classes _should_ be in the classpath, right?
What really bothers me is that I can get it to run in fortress, but not in
merlin. I've been battling this one all day today. Anyone else have a clue
on where to start looking for the bug?
I really appreciate any help. Thanks!
J. Aaron Farr
� SONY ELECTRONICS
� DDP-CIM
� (724) 696-7653
�
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
