[news.eclipse.technology.ecf] Re: ECF, JMS, and Something Scott Said

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Geoffry,

Geoffry Roberts wrote:
> All,
>
> I would like to add JMS capability to my current OSGi based 
> application.  I have been looking at ECF and its ActiveMQ support, and 
> yes I'm having problems.
>
> The bundle org.eclipse.ecf.provider.jms.activemq shows up in equinox as 
> active, but I can't connect. I get "connection refused" when I attempt 
> to create the connection.  In stepping through the code, I have noticed 
> the use of "defaultUser" and "defaultPassword".  Are these valid?


Yes...at least as of version 3.1 of ActiveMQ.  I'm not sure about more 
recent versions.

> Here's what I have:
>
> ActiveMQConnectionFactory connectionFactory = new 
> ActiveMQConnectionFactory(
>                 "tcp://localhost:61616");
> connection = connectionFactory.createConnection();
>             session = connection.createSession(false, 
> Session.AUTO_ACKNOWLEDGE);
> ..
>
> I saw in another thread Scott recognizing the need for more 
> documentation and wanting to know what might be needed.  Well, I could 
> use a little HowTo wrt ECF and JMS.


The first thing to add is a started activemq broker.  That is, somehow 
you need to have a running activemq broker...at the given port 
(61616...which is the default for at least the older versions of activemq).

Here's a web page on running activemq as a separate java process:

http://activemq.apache.org/run-broker.html

I understand it's also easily run inside WebSphere Community Edition, 
although I'm not sure if that's still the case.

Once the broker is started and listening, you need to start an ECF 
Generic server, and have the generic server connect to the broker. 
There's an ECF ActiveMQ server application called 
org.eclipse.ecf.provider.jms.ActiveMQServer that does this.

I've also just put a launch configuration into the 
org.eclipse.ecf.provider.jms.activemq project/bundle...and made it a 
little bit simpler, so you should get the latest of this project from 
ecf1.osuosl.org.

Once you've got the broker running, and the ECF generic activemq server 
running and connected to the broker, then you should be able run/start 
the clients, connect to the ECF generic activemq server, etc.

> Also,
>
> I see that the current ECF ActiveMQ is based on v3.1.  Is there any plan 
> to update to v5? 


I would like to do this right away, but I can't currently tackle it 
myself.  I would suggest opening an enhancement request at 
http://bugs.eclipse.org, however, and perhaps we can get multiple 
contributors...and I will help, of course.  If activemq has been pretty 
good about remaining backward compatible it might not be difficult at all.

Thanks,

Scott