Hi Erik, The MEP (Message Exchange Pattern) then is asynchronous messaging two way. Architecturally you should expose your web-service in the UI-service layer and have that UI layer update your domain layer object(s) and consume your partners web-service from the SI layer and have that SI layer inject (DI) data into your domain layer object(s) Typical architecture layers for an rich domain application: (UI --> PD <-- SI) (with arrows showing direction of dependency). UI = User Interface (User could be human or a system consumer), PD = Problem Domain (the Rich Domain Model). SI = Service Interface layer (the code that consumes services from other systems)
So this is what you need to do from an application layer point of view: Partner Consumer ---> UI --> PD <-- SI ---> Partner Producer. Easy and proven pattern to follow. Pretty much described by the Hexagonal Architecture [1] [1] http://alistair.cockburn.us/Hexagonal+architecture In this endeavor (others please correct me if I am wrong), there is nothing in ISIS that assists you in speeding up such integration except if you were prepared to accept the generated RO UI and expose that to your partner. Regards,David. On Saturday, 31 October 2015 1:24 AM, Erik de Hair <e.deh...@pocos.nl> wrote: On 10/30/2015 12:44 PM, Dan Haywood wrote: > Is your application the web services client (will it be making calls to a > Web service exposed by your supplier) or is it the other way around (you > need to expose a web service for your suppliers to call)? We have to expose a web service for our suppliers to call. Our suppliers have a web service to order and confige services that will be called by our application. The supplier's web service will send a message (asynchronously) to our webservice (to be created) when an order status changes. We have to update the order in our application after this message is received. This process is dictated by our supplier. So our application will be both web service and client in this process but the client part is no problem. Erik > > I'm guessing the former because you mentioned XML rather than JSON so > perhaps this is a SOAP service that already exists? > > Dan > On 30 Oct 2015 10:03 am, "Erik de Hair" <e.deh...@pocos.nl> wrote: > >> Hi, >> >> We have to create a webservice to receive XML-messages from suppliers. As >> a result some entity in our Isis application has to be updated. Is there >> any way to realise this in a proper way in Isis? >> >> Thanks, >> Erik >>
