Hi, Now we use a home-grown service router (service bus, protocol translator) to keep control of our services. The architecture is like this: [Facades]-->[Adapters, Converters]-->[DAOs]
A Facade can be a EJB, a JSP or a Webservice. Adapters or Converters are POJOs that mix or transform services (messages). DAOs (Data Access Objects) are Objects that access other systems like a JDBC call, a RMI-call or a call to a webservice. All components are glued together with Spring and deployed as EAR-file on a J2EE server. (Until now all calls are synchronous.) Now we want to replace and expand this thing with a standard-tool. As far as I understand, in ServiceMix this would read like [Consuming BC]-->[NMR + SEs]-->[Providing BC] Now the question is, whether ServiceMix could do the job. As I understand the problem is the EJB as consuming BC. It is not easy (possible?) to do this in ServiceMix 3. Is this right? As I understand ServiceMix 4.0 would satisfy our requirements (true?), but we would have to "wait for a few months" as I read in another posting. Is there a rough estimate how many these "few" month are such that we could use SMX4 as service router between stateless EJBs, JSPs, webservices (ie. use RMI, HTTP, SOAP in a consuming BC)? Greetings Erhard -- View this message in context: http://www.nabble.com/Wait-for-SMX4-to-use-RMI--tp14777867s12049p14777867.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
