I am starting a new project where I want to have a .net client because we have a good amount of .Net GUI expertise we want to leverage. However, most of our server side code is based on EJBs and for good reason. We deploy to Unix machines and would like to keep the server Java centric. I could easily expose our services as web services but we want the client to be loosely coupled to the services and thus asynchronous. Plus synchronous RPC is a 4 letter word around here.
As the message bus we don't really care what we use. ActiveMQ for example offers .Net interoperability. Red Hat is also working on a generic messaging solution based on JBoss Messaging. Is anyone working on these types of solutions? Are solutions for asynchronous Web Services already out there that I can use? How are you guys solving these issues?
If you have any ideas on implementation, it will be greatly appreciated.
posted 8 years ago
Expose the ejbs as a web service. Then call the web service from the dot net client. [ September 20, 2007: Message edited by: Jesus Angeles ]