-
1. Re: Native services in ESB
burrsutter Sep 18, 2007 1:18 PM (in response to rachmato)As it relates to Web Services:
Native using the org.jboss.soa.esb.actions.soap.SOAPProcessor
Non-Native using org.jboss.soa.esb.actions.soap.SOAPClient
Native means it is based on JBossWS and hosted within our container.
Non-Native means it is normally external to our container (e.g. a .NET service).
Does that help a little?
Burr -
2. Re: Native services in ESB
marklittle Sep 18, 2007 3:28 PM (in response to rachmato)The definition should be irrespective of the transport.
A native ESB service, aka ESB-aware service, is on that understands the Message format directly and without the aid of an intermediary or adapter (e.g., gateway).
A non-native service is one that is deployed outside of the ESB and communicates using a data format that is not supported directly by ESB-aware services. It needs an adapter (e.g., gateway) to interact with services/consumers. -
3. Re: Native services in ESB
rachmato Sep 18, 2007 5:42 PM (in response to rachmato)Thanks, that does help a little. Does that mean there will be similar paris of methods
org.jboss.soa.esb.X.XProcessor
org.jboss.soa.esb.X.XClient
for every other 'preexisting' or legacy service (EJBs, Spring-POJOs, ...) which we want to acces from the ESB? -
4. Re: Native services in ESB
burrsutter Sep 18, 2007 5:58 PM (in response to rachmato)Not really. EJBs can be handled via their remote interface therefore can be local or remote. Spring has its own action that assumes it is local.
By "local" I mean in the same container/JVM.
We do have quickstarts for both SLSB and Spring POJOs that demonstrate how to interact. So while not the same exact technique it is close. The difference is that with SOAP/XML you can essentially generate a client on the fly. With Spring & EJB that is a little bit harder.
Burr