wood burning stoves 2.0*
The moose likes Web Services and the fly likes Back-end communication between WS and Java app Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Back-end communication between WS and Java app" Watch "Back-end communication between WS and Java app" New topic
Author

Back-end communication between WS and Java app

aaa sss
Greenhorn

Joined: Jul 12, 2011
Posts: 1
I'm developing a web service which should notify a Java application when it receives a particular SOAP message. So far I've considered using a database table (overkill), sockets (simple but not elegant) and JMS. It's been suggested to use an Enterprise Service Bus like Apache Synapse but that seems like overkill. Any other suggestions?

Are there any particular drawbacks to JMS in this case?

Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
I wouldn't say that using a database table is always overkill - sometimes it may be, but there are times it is a justified solution. It depends on the circumstances.
JMS is also a good alternative, but has some drawbacks like, for instance, not being able to consume an arbitrary pending message.
Finally, I also want to say that using an ESB is not necessarily overkill. I have only worked with Mule, but I feel that it can be justified due to the speed with which you can develop.
If you want a more detailed answer, please describe your scenario in slightly greater detail.
Best wishes!


My free books and tutorials: http://www.slideshare.net/krizsan
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Back-end communication between WS and Java app
 
Similar Threads
JMS reference
updating web page with events
JMS for data pulling
keeping http clients up to date
Socket server inside Tomcat