This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
My application is running on Weblogic 8.1 and I am sending messages to another application on a different server which is also Weblogic 8.1.
Since both of them are on the same weblogic version, I am not using messaging bridge. Can anyone shed light on pros and cons of using a messaging bridge in this scenario. Should I be using messaging bridge?
If yes, I would appreciate if anyone can guide me what changes need to be done as far as code is concerned. I know how to configure the bridge and bridge destinations on the console but not sure what different i need to do in my MDB.
The big advantage to using the WebLogic Messaging Bridge here is twofold:
1) Your client code does not need to know the location of the other WebLogic Server in order to send it the JMS Message. The Messaging Bridge will still need to be configured with this information in the WebLogic Console... it just keeps it out of your code.
2) WebLogic Messaging Bridge helps facilate sending messages between different versions of WebLogic (which used to be a real pain due to JMS differences in versions). So I would be tempted to lean towards using the Message Bridge just so your Servers can upgrade to subsequent versions of WebLogic more easily.
As for your last question... no your MDB should not need to be changed. The Messaging Bridge is just taking care of getting the messages to the other Server... you MDB still needs to do its processing against a Queue or Topic like normal.
Moving to the BEA/WebLogic Forum for more discussion...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com