Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
completeTask is a C ONTINUE method: Calls to CONTINUE and FINISH methods must specify a valid existing key for the target conversation. Non-Workshop SOAP clients should do this by including a conversationID element in the SOAP header, per the WSDL
com.bea.wlw.runtime.core.request.RequestValidationException: completeTaskis aCONTINUE method:Calls to CONTINUE and FINISH methods must specify a valid existing keyforthe target conversation.Non-Workshop SOAP clients should do this by including a conversationIDelement in the SOAP header, per the WSDL description.Workshop clients must reference a properly annotated CTRL (not a WSDL)file:make sure an @jws:conversation annotation with the appropriate valueexists for this method in the CTRL. at com.bea.wlw.runtime.core.request.BaseRequest.validateTarget(BaseRequest.java:282) at com.bea.wlw.runtime.core.request.ExecRequest.validateTarget(ExecRequest.java:204) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:65) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:285) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:240) at $Proxy84.completeTask(Unknown Source) at notification.taskDetails.TasksDetailsController.changeState(TasksDetailsController.jpf:497)