One of the simplest yet most useful aspects of the LC ES Service model is that all Services have a WSDL; be they Services that we provide out of the box, Services that you write using custom component development or even processes that you author using Workbench. One problem is that there are so many ways that you can actually call a Web Service. Our SDK Guru Scott MacDonald has put together a great new guide for writing applications that call LiveCycle Web Services: Latest Web Service Guide
How many ways can you call a Web Service?
April 23, 2008 by ggilchri
This is a great guide. Many thanks for posting this. There are a couple of things I’d like to see added:
- As I understand it, DIME is on its way out and is being replaced by MTOM. It would be nice to see an MTOM approach added to the document.
- Invoking LiveCycle from .NET is only half the story. Illustrating how to invoke a .NET web service from within a LiveCycle orchestration would also be helpful. The current LiveCycle ES SOAP component only supports SwA which .NET doesn’t directly support.
We’ve encountered both the need to pass a PDF via a web service call from .NET to LiveCycle and vice-versa. This paper will help us improve the way we do the former. We’re in the process of implementing an MTOM based solution for the latter.
Rob
HI
Thanks for the comments. As of LiveCycle ES 8.2 – LiveCycle does not yet support MTOM. I think this is stated on the first page
If you do not want to use DIME or base64 – you can use BLOB data over HTTP.
Scott
> LiveCycle does not yet support MTOM.
Technically, LiveCycle doesn’t support DIME either, right? Technically, it’s the Apache proxy code that supports DIME and then it calls LiveCycle using Java interface methods, or am I missing something?
Couldn’t one use MTOM instead of DIME by using similar proxy code?
Rob
Looks like the upcoming LiveCycle ES 2.0 will support MTOM. However, LC ES 2.0 will be coming late 2009.