Error creating bean with name ‘queueSender’: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.springframework.jms.core.JmsTemplate]: Error creating bean with name ‘jmsTemplate’ defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean ‘connectionFactory’ while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘connectionFactory’ defined in ServletContext resource [/WEB-INF/applicationContext.xml]: 1 constructor arguments specified but no matching constructor found in bean ‘connectionFactory’ (hint: specify index and/or type arguments for simple parameters to avoid type ambiguities)

did any one run into the same error?

This blog post have been very helpful because “it just makes more sense to use a synchronous request/response” as you said ;o)

By the way, I am not sure I have understood how to use the permanent response queue. Does it mean that the request queue listener have to use a queue sender to send a response to the initial requester (that is waiting an answer on the response queue)? Or there is a smarter way to code that? How the queue listener should be coded to use the response queue?

Thanks!

Sure it does. Observe:

byte[] invalidUTF8 = {-128};
String mystery = new String(invalidUTF8, “UTF-8″);
print((int) mystery.charAt(0));
// prints 65533

.. and 65533, FFFD in hex, happens to be REPLACEMENT_CHARACTER in Unicode.