Invoking a human-centric long-lived process using the web service API
5 views
Skip to first unread message
exwil
unread,
Jun 29, 2009, 11:26:48 AM6/29/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Adobe LiveCycle Developers
I've created a service link in my .NET application and
JobManagerService proxy class was generated. BUT the instance of
JobManagerService class doesn't have any "getResult" methods.
How I can get the results of asynchronous call if I use web service
walkthrough ?
Thanks in advance.
Help topic:
"Invoking a human-centric long-lived process using the web service
API"
Retrieve the results :
• Create a Microsoft .NET client assembly that consumes the Job
Manager service WSDL. (See Creating a .NET client assembly that uses
base 64 encoding.)
• Reference the Microsoft .NET client assembly. (See Referencing
the .NET client assembly.)
• Create a JobManagerService object by using its constructor.
• Create a JobId object by using its constructor.
• Set the JobId object’s id data member with the return value of the
MortgageLoanPrebuiltService object’s invoke_Async method.
• Assign the value true to the JobId object’s persistent data member.
• Create a JobStatus object by invoking the JobManagerService object
‘s getStatus method and passing the JobId object.
• Get the status value by retrieving the value of the JobStatus
object’s statusCode data member.
There is NO action to get the return parameters!
exwil
unread,
Jul 10, 2009, 12:19:51 PM7/10/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Adobe LiveCycle Developers
I've found a temp solution to achieve my goal. I created a new
livecycle process with only 1 JavaExecute service. The process has
only 1 input parameter - jobID and returns results of long-lived
processes invoking. Investigation to be continued...