Posts

Showing posts from June, 2009

Drools Configurations

Message Driven POJOs!

Image
Message Driven POJOs! Posted on August 11th, 2006 by Mark Fisher in 2.0 , JMS , Spring . Of all the new Spring 2.0 features and improvements, I must admit that Message-Driven POJOs are one of my personal favorites. I have a feeling that a lot of other Spring users will feel the same way. Here I am providing a quick introduction. There is a lot more to show, and I will follow this up with other posts. For now though - this should provide you with enough information to get up and running with some truly POJO-based asynchronous JMS! I hope you are as excited about that as I am Prerequisites: You will need the following JAR files on your classpath. I've also listed the versions that I am using (any spring-2.x version should be fine. I just dropped RC3 in there about 2 minutes ago in fact): activemq-core-3.2.2.jar concurrent-1.3.4.jar geronimo-spec-j2ee-managment-1.0-rc4.jar commmons-logging-1.0.4.jar log4j-1.2.9.jar jms-1.1.jar spring-2.0-rc3.jar Setup the En

ActiveMQ 5.1.0 tutorial

It is always good to know at least one message brokers. ActiveMQ is one of those top brokers used actively industry wide. So, here is a small tutorial or tips to use ActiveMQ along with java messaging service. Installations I am using the following configuration on my system: 1. Windows XP 2. JDK 5 update 15 3. ActiveMQ 5.1.0 Download activeMQ from http://activemq.apache.org/ . Unzip to any suitable location. And the installation is done!!! Directory Structure After you unzip, there are few basic files you need to know. a. The bin folder contains the batch file, activemq.bat, using which you can start the server. It also contains activemq-admin.bat, using which you can get more details about activemq, like a listing of queues etc. b. The conf folder contains the activemq.xml configuring the ActiveMQ broker. Here is where we can configure the transports, permanent queues etc. Creating Temporary Queues Firt run bin/activemq.bat. This should start ActiveMQ listening at port 61616. There i