Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » SeMantic Information Logistics Architecture (SMILA) » Irrelevant parameter in JMS extension point?
Irrelevant parameter in JMS extension point? [message #661906] Mon, 28 March 2011 13:38 Go to next message
SMILANewBee is currently offline SMILANewBee
Messages: 42
Registered: August 2010
Member
Hello,

we have replaced the ActiveMQ broker through the HornetQ and implemented a new bundle that makes contributions to the "org.eclipse.smila.jms" extension point. There are two parameters of the element "access": the class that implements the "MQAccess" interface and the factory class for the JMS system.

The MQAccess class provides a factory for the ConnectionFactory. So with this class SMILA has access to the ConnectionFactory. So why does SMILA need the second parameter?
Re: Irrelevant parameter in JMS extension point? [message #662015 is a reply to message #661906] Mon, 28 March 2011 21:40 Go to previous messageGo to next message
Igor Novakovic is currently offline Igor Novakovic
Messages: 53
Registered: July 2009
Member
Hi,

Integrating HornetQ in SMILA sounds very interesting!
Could you please share more information with us about this?
Is there perhaps a chance for you to share this code with community?

Cheers
Igor

Am 28.03.2011 15:38, schrieb SMILANewBee:
> Hello,
>
> we have replaced the ActiveMQ broker through the HornetQ and implemented
> a new bundle that makes contributions to the "org.eclipse.smila.jms"
> extension point. There are two parameters of the element "access": the
> class that implements the "MQAccess" interface and the factory class for
> the JMS system.
>
> The MQAccess class provides a factory for the ConnectionFactory. So with
> this class SMILA has access to the ConnectionFactory. So why does SMILA
> need the second parameter?
Re: Irrelevant parameter in JMS extension point? [message #662091 is a reply to message #661906] Tue, 29 March 2011 08:46 Go to previous message
Andreas Weber is currently offline Andreas Weber
Messages: 24
Registered: July 2009
Junior Member
Hi,

I'm not totally familiar with that part of the code, but I had a look
and think you are right. The "connectionFactoryClass" param is actually
unnecessary.

It seems that it's just used to check if it fits to the
'ConnectionFactory' setting of the queue worker connection configuration
(configuration/org.eclipse.smila.connectivity.queue.worker.j ms/QueueWorkerConnectionConfig.xml).


But I don't see any generic handling here for using different configs
for different JMS providers or sth. like that...

So we should think about a code cleanup here. But until that happened
you should just be able to workaround that by using the value set in
QueueWorkerConnectionConfig.

Cheers,
Andreas


Am 28.03.2011 15:38, schrieb SMILANewBee:
> Hello,
>
> we have replaced the ActiveMQ broker through the HornetQ and implemented
> a new bundle that makes contributions to the "org.eclipse.smila.jms"
> extension point. There are two parameters of the element "access": the
> class that implements the "MQAccess" interface and the factory class for
> the JMS system.
>
> The MQAccess class provides a factory for the ConnectionFactory. So with
> this class SMILA has access to the ConnectionFactory. So why does SMILA
> need the second parameter?
Previous Topic:Demos wanted: SMILA Conference / 29.6.2011, Berlin --> Please answer end of week
Next Topic:0.8 M1 is out!
Goto Forum:
  


Current Time: Fri Oct 24 09:37:58 GMT 2014

Powered by FUDForum. Page generated in 0.02193 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software