Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.3-rc1
-
Fix Version/s: 1.3
-
Component/s: Documentation / Website, Transport: JMS
-
Labels:None
-
Environment:
Snapshot (downloaded approx 10 february 2005). JDK 1.5.0_06 (Win32)
-
Configuration:
-
Similar Issues:None
Description
I tried to use Oracle AQ support in a Mule 1.3 snapshot.
I use the sample at: http://mule.codehaus.org/Oracle+AQ+Integration
Notice there is a small typo in the className attribute of the oracleJmsConnector. It should say "org.mule.providers.oracle.jms.OracleJmsConnector" instead of "org.mule.vendor.oracle.jms.OracleJmsConnector"
I get the following traceback
Either the documenation is wrong "Unlike the standard JMS Provider, the Oracle JMS Provider does not require a JNDI provider to use.", or the following is caused by a bug.
********************************************************************************
Message : The required object/property "jndiInitialFactory" is null
Type : org.mule.umo.lifecycle.InitialisationException
Code : 72045
JavaDoc : http://mule.codehaus.org/docs/apidocs/org/mule/umo/lifecycle/InitialisationException.html
********************************************************************************
Exception stack is:
1. The required object/property "jndiInitialFactory" is null (org.mule.umo.lifecycle.InitialisationException)
org.mule.providers.jms.JmsConnector:145 (http://mule.codehaus.org/docs/apidocs/org/mule/umo/lifecycle/InitialisationException.html)
********************************************************************************
Root Exception stack trace:
org.mule.umo.lifecycle.InitialisationException: The required object/property "jndiInitialFactory" is null
at org.mule.providers.jms.JmsConnector.initJndiContext(JmsConnector.java:145)
at org.mule.providers.jms.JmsConnector.doConnect(JmsConnector.java:228)
at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:787)
...
Can you please fix the documentation and
Please try this with the main source tree (2.x) instead of 1.3, I'm pretty sure it's already fixed there and the fix has not yet been merged into the 1.3 branch.