Mustafa

For some reason my mails keep getting rejected as the mail server thinks its spam..
anyway.. here is what I wanted to let you know

This is what we do at that line:
       context = new InitialContext(jndiProperties);
       conFactory = (ConnectionFactory) context.lookup(connFactoryJNDIName);
       log.info("Connected to the JMS connection factory : " + 
connFactoryJNDIName);

       try {
           ConnectionFactory conFac = null;
           QueueConnectionFactory qConFac = null;
           TopicConnectionFactory tConFac = null;
if (JMSConstants.DESTINATION_TYPE_QUEUE.equals(getConnectionFactoryType())) {
*                qConFac = (QueueConnectionFactory) conFactory;*
....

So, it seems like what is bound to JNDI as the JMS connection factory does not implement the javax.jms.QueueConnectionFactory interface.. maybe this is a known issue with AQ?

However, what I do not quite understand is how the sample JMS client that Greg tried worked with AQ.. his code contains the following lines:

queueConnectionFactory = (QueueConnectionFactory) 
jndiContext.lookup("java:comp/env/jms/PlayerConnectionFactory");Re: Switching 
transports - JMS to http using AQ
queue = (Queue) jndiContext.lookup(queueName);


asankha

Reply via email to