Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Calling long lived process with webservices

Avatar

Former Community Member

Hi all, I've been following the sample here

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/001468.html

And tweaking it for my own solution. The only thing is that my solution is a long lived, and i'm getting an error saying that my long lived service cannot be invoked synchronously. My question is, how would i call it asynchronously? I know that with the s ervlet api you specify it in the parameter of the invoke method, but i'm not sure with webservices.

Thanks

Billy

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Billy,

Instead of invoke() method did you try invoke_Async()?

Parth Pandya

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

Hi Billy,

Instead of invoke() method did you try invoke_Async()?

Parth Pandya

Avatar

Former Community Member

Yep, that work, thx very much. Just out of curiosity is there a LiveCycle resource where this is mentioned?

Avatar

Former Community Member

Thanks Jasmin. I was looking for a java reference/sample, i guess thats why i didn't find it.

Thanks again!

Billy

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----