xsd - Error orchestrating web service deployed in azure with Apache ODE -

i trying orchestrate web service deployed in windows azure apache ode. testing services eclipse integrated web service explorer. azure ws works fine when test artifacts.wsdl throws following error:

14:41:38,777 info  [deploymentpoller] deployment of artifact bpel_process successful: [{http://artifacts}process-132] 14:41:49,474 warn  [simplescheduler] dispatching jobs more 5 minutes delay. either server down time or job load greater available capacity 14:41:57,594 warn  [externalservice] fault response: faulttype=(unkown) <?xml version='1.0' encoding='utf-8'?><s:envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:body><s:fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:internalservicefault</faultcode><faultstring xml:lang="en-us">the server unable process request due internal error.  more information error, either turn on includeexceptiondetailinfaults (either servicebehaviorattribute or &lt;servicedebug> configuration behavior) on server in order send exception information client, or turn on tracing per microsoft .net framework 3.0 sdk documentation , inspect server trace logs.</faultstring></s:fault></s:body></s:envelope> 14:41:57,620 error [invoke] failure during invoke:  14:41:57,623 info  [bpelruntimecontextimpl] activityrecovery: registering activity 15, failure reason:  on channel 27 

here files:

process.bpel

artifacts.wsdl

mod2.wsdl

mod2.xsd

edit when add includeexceptiondetailinfaults in web service:

17:51:49,762 warn  [externalservice] fault response: faulttype=(unkown) <?xml version='1.0' encoding='utf-8'?><s:envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:body><s:fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:internalservicefault</faultcode><faultstring xml:lang="en-us">object reference not set instance of object.</faultstring><detail><axis2ns1:exceptiondetail xmlns:axis2ns1="http://schemas.datacontract.org/2004/07/system.servicemodel" xmlns:i="http://www.w3.org/2001/xmlschema-instance"><axis2ns1:helplink i:nil="true" /><axis2ns1:innerexception i:nil="true" /><axis2ns1:message>object reference not set instance of object.</axis2ns1:message><axis2ns1:stacktrace>   @ wcfservicewebrole1.azureimpl.mod2(string arg0)&#xd;    @ syncinvokemod2(object , object[] , object[] )&#xd;    @ system.servicemodel.dispatcher.syncmethodinvoker.invoke(object instance, object[] inputs, object[]&amp; outputs)&#xd;    @ system.servicemodel.dispatcher.dispatchoperationruntime.invokebegin(messagerpc&amp; rpc)&#xd;    @ system.servicemodel.dispatcher.immutabledispatchruntime.processmessage5(messagerpc&amp; rpc)&#xd;    @ system.servicemodel.dispatcher.immutabledispatchruntime.processmessage31(messagerpc&amp; rpc)&#xd;    @ system.servicemodel.dispatcher.messagerpc.process(boolean isoperationcontextset)</axis2ns1:stacktrace><axis2ns1:type>system.nullreferenceexception</axis2ns1:type></axis2ns1:exceptiondetail></detail></s:fault></s:body></s:envelope> 17:51:49,798 error [invoke] failure during invoke:  17:51:49,801 info  [bpelruntimecontextimpl] activityrecovery: registering activity 15, failure reason:  on channel 27 

still no clue of means. eclipse points out en error on bpel file. <copy> tag under <assign> throws:

the from-spec of "<xs:simpletype "string">" not compatible to-spec of "<xs:complextype>" ignored because following xsd schemas doesn't make sense me , disappears.

edit ii:

as mentioned @vanto <assign> activity wrong. had add prefix of namespace of wsdl cdata tag:

<bpel:query querylanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">   <![cdata[mod2:mod2result]]> </bpel:query> 

still don't understantand namespaces seems related fact had add elementformdefault="qualified" xsd imported wsdl of azure service.

the error means ode got soap fault response. indicates invoked web service raised exception. please check logs of web service or turn on includeexceptiondetailinfaults feature in order details went wrong. please not ode not validate outgoing messages, if <assign> activities not create correct request, ode won't notice invoked service complain.