Frustrated that using OJMS/AQ requires using direct AQ apis

Question

Well, I'm sure I could be mistaken, but I'm coming to the conclusion that in order to get a workable JMS implementation with OC4J 9.0.2, you have to use AQ (this is known), but what is a surprise to me is that I am unable to get a raw JMS consumer and producer working without coding specific usage of the AQ api on both ends. Note that I'm trying to have a consumer process that is a standalone Java process, whereas the producer will be in EJB session code.
It appears to be a little easier if you're using MDBs, but I am not.
In particular, there appears to be no way to get a QueueConnectionFactory using the standard JMS api. You have to use the "AQjmsFactory.getQueueConnectionFactory()" method.
Once I got past that, I discovered that my normal JMS-compliant lookups through JNDI for the queue name were not working. It's entirely possible I'm using the wrong name, but I've tried several different variations. So, I plugged in the "AQjmsSession.getQueue()" method. Not only is this another AQ-specific API, but I now have to get this in a different order than I did when using JMS-specific APIs. That is, I now have to have a QueueSession before I can get the Queue, which I didn't have to do with the JNDI lookup.

Answer 1

Vivek,
I get the following error message (JMS Error: invalid arguments in call). If I remove the connection factories specification in the orion-ejb-jar.xml this error goes away but the application does not run.
[c:/tools/OC4J_9.03/j2ee/home> java -jar oc4j.jar
Auto-unpacking C:\tools\OC4J_9.03\j2ee\home\applications\chapter07.ear... done.
Auto-unpacking C:\tools\OC4J_9.03\j2ee\home\applications\chapter07\chapter07-web
.war... done.
Auto-deploying chapter7 (Assembly had been updated)...
Error deploying file:/C:/tools/OC4J_9.03/j2ee/home/applications/chapter07/chapte
r07-ejb.jar homes: JMS Error: invalid arguments in call
Auto-deploying file:/C:/tools/OC4J_9.03/j2ee/home/applications/chapter07/chapter
07-web/ (Assembly had been updated)...
Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized
[c:/tools/OC4J_9.03/j2ee/home>
Here are my configuration files:
=======================> orion-ejb-jar.xml <==================================
<orion-ejb-jar>
   <enterprise-beans>
   <message-driven-deployment name="ProcessApprovalMessageBean"
     destination-location="java:comp/resource/ojms/Topics/AQ_ADM.PROCESSTOPIC_Q"
     connection-factory-location="java:comp/resource/ojms/TopicConnectionFactories/theTopicConnectionFactory"
     subscription-name="topicSubscriber" >
    <resource-ref-mapping name="jms/emailMessageQueue"
        location="java:comp/resource/ojms/Queues/AQ_ADM.EMAILQUEUE_Q" />
    <resource-ref-mapping name="jms/emailMessageQueueConnectionFactory"
        location="java:comp/resource/ojms/QueueConnectionFactories/theQueueConnectionFactory" />
   </message-driven-deployment>
   <message-driven-deployment name="EmailMessageBean"
     destination-location="java:comp/resource/ojms/Queues/AQ_ADM.EMAILQUEUE_Q"
     connection-factory-location="java:comp/resource/ojms/QueueConnectionFactories/theQueueConnectionFactory">
   </message-driven-deployment>
   </enterprise-beans>
   <assembly-descriptor>
      <default-method-access>
         <security-role-mapping name="&lt;default-ejb-caller-role&gt;" impliesAll="true"/>
      </default-method-access>
   </assembly-descriptor>
</orion-ejb-jar>
=======================> ejb-jar.xml <==============================================
<ejb-jar>
   <enterprise-beans>
     <message-driven>
         <description></description>
         <ejb-name>ProcessApprovalMessageBean</ejb-name>
         <ejb-class>purchase.ejb.mdb.ProcessApprovalMessageBean</ejb-class>
         <transaction-type>Container</transaction-type>
         <message-driven-destination>
           <destination-type>javax.jms.Topic</destination-type>
           <subscription-durability>Durable</subscription-durability>
         </message-driven-destination>
         <resource-ref>
            <description>The topic for EmailMessage</description>
            <res-ref-name>jms/emailMessageQueue</res-ref-name>
            <res-type>javax.jms.Queue</res-type>
            <res-auth>Container</res-auth>
         </resource-ref>
         <resource-ref>
            <description>The Factory used </description>
            <res-ref-name>jms/emailMessageQueueConnectionFactory</res-ref-name>
            <res-type>javax.jms.QueueConnectionFactory</res-type>
            <res-auth>Container</res-auth>
          </resource-ref>
     </message-driven>
     <message-driven>
      <description>EmailMessageBean</description>
         <ejb-name>EmailMessageBean</ejb-name>
         <ejb-class>purchase.ejb.mdb.EmailMessageBean</ejb-class>
         <transaction-type>Container</transaction-type>
         <message-driven-destination>
           <destination-type>javax.jms.Queue</destination-type>
         </message-driven-destination>
      </message-driven>
   </enterprise-beans>
</ejb-jar>
============================> resource provider in application.xml <=======================
<resource-provider
      class="oracle.jms.OjmsContext"
      name="ojms">
       <description>
          Oralce JMS resource provider.
       </description>
       <property name="url"
       value="jdbc:oracle:thin:@hostname:1521:sid"/>
       <property name="username" value="user"/>
       <property name="password" value="password"/>
    </resource-provider>
======================> end of configuration file changes <========================
Is this the only thing I need to do?
thanks
Mathew