Ah, just re-read the email subject line, so, yes, you are consuming an already existing web service.
So, you could surface the data within that Web service using a view model. Is there a Wsdl? If so you could use that to generate java dto classes and have the view model use them within its viewModelMemento() and viewModelInit() methods. Using a view model assumed that there's an end user that's responsible for manually interacting with the suppliers wen service, ie there's some external business process (eg they receive an email) so that they know to invoke the action that's going to hit the external service. If that's not the case, then an alternative design might simply be to use quartz or camel to poll the supplier's Web service periodically (hourly, daily) and do the necessary. Hth, Dan. On 30 Oct 2015 11:44 am, 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)? > > 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" <[email protected]> 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 >> >
