-
1. Re: Migartion from javax.jms,(OpenJms) to JbossMessaging
saltnlight5 Aug 23, 2010 9:40 AM (in response to rahul9885)1) You might want to post to JBossMessaging forum instead.
2) JBoss's next generation of messaging product is called HornetQ, and it will be default JBoss6, so check it out.
3) If you used standard javax.jms api, then your code will not change much. If you used anything OpenJMS specific, obviously you need to replace equavalent with JBossMessaging.
4) What about the server? JBossMessaging is the message broker/server, just as OpenJMS. So... your question is?
be specific with your question and you get better answer.
-
2. Re: Migartion from javax.jms,(OpenJms) to JbossMessaging
rahul9885 Aug 24, 2010 11:38 AM (in response to saltnlight5)Dear Zemian,
Thanks for reply .
Basically in my application exolab's Openjms source code is been used like below :
import javax.jms.Message;
import org.exolab.jms.selector.Selector; // source code fileclass Evaluator {
protected Evaluator(){}
public Evaluator(String expression) throws InvalidSelectorException
{
m_selector = new Selector(expression); // creating selector Object
}public boolean evaluate(Map params)// here Map is passed as argument
{
return evaluate(new MessageSelectionFacade(params));
}public boolean evaluate(Message msg){
return m_selector.selects(msg); // receiving message using selects()
}}
This is the only file where application is using openJms's source code.
In other java files "JMS clients (producer & consumer)" is written using javax.jms package.
We are migrating fron OpenJmS (MS provider Jms Server) to Jboss Messaging ( jboss-4.3.0).
So In this case are the configuration change we have to undergo to run Jboss Messaging (JMS Server)
Any help would be greatly appreciated!!!
Thanks and Regards,
Rahul Aahir
mail : rahul.aahir@tcs.com