Vikas, ODE does not support remote WSDLs. That's because we don't really want to deal with the implications, like what should happen if a WSDL changes while the process is deployed or running.
The recommended solution is to download the remote WSDL and place it locally in the deployment unit. That way you have the control about the file. HTH, Tammo Garg, Vikas wrote: > Hi Tammo, > > Thanks for your response. It works if I place the wsdl within the deployment > unit and organize the imports. Extremely thanks for your help. > > I have a question - In the above case, I am just invoking a simple hello > world web service which was written by me, so I could place the wsdl file > into the deployment unit. But what if I want to access the web service hosted > by someone and I just have wsdl URL with me to invoke that web service. In > such cases, I just add the http url of the wsdl in the imports (say for > example, http://<hostname>/../SampleService.svc?wsdl), but I get the error as > follows. > > FATAL - GeronimoLog.fatal(116) | openResource: invalid scheme (should be > urn:) http://<hostname>/../SampleService.svc?wsdl > > Now, what needs to be done in such cases since it is already an urn? Is there > any configuration in ODE that we need to do in order to invoke an external > webservice using the URL? > > Any ideas? > > Thanks, > Vikas > > > -----Original Message----- > From: Tammo van Lessen [mailto:[email protected]] > Sent: Friday, March 26, 2010 5:51 PM > To: Garg, Vikas > Subject: Re: Issue with deploying BPEL process into Apache ODE > > Vikas, > > it's very difficult to guess. The error means, that ODE cannot find the > definition for the given service QName. It tries to lookup in the WSDL > doc registry. Please try to place your WSDL within the deployment unit > and/or reorganize the imports. > > HTH, > Tammo > > Garg, Vikas wrote: >> Can someone please respond as what needs to be done in order to resolve the >> issue mentioned in my below email? I have attached all the files along with >> this email as well. >> >> Help in any form would be appreciated. >> >> Thanks for your time, >> Vikas >> >> -----Original Message----- >> From: Garg, Vikas [mailto:[email protected]] >> Sent: Thursday, March 25, 2010 8:41 PM >> To: [email protected] >> Cc: [email protected] >> Subject: RE: Issue with deploying BPEL process into Apache ODE >> >> Hi, >> >> Thanks for the information. Using file:// before the path took me one step >> ahead and now I get another exception shown below. >> >> ERROR - GeronimoLog.error(104) | Latch error, was releasing for state 1 but >> actually in -1 WARN - GeronimoLog.warn(96) | Deployment failed within the >> engine, store undeploying process. >> org.apache.ode.bpel.iapi.ContextException: Cannot find definition for >> service {http://test.ptc.com}SampleHelloWSService in the context of process >> {http://caller}Caller-1 >> at >> org.apache.ode.axis2.BindingContextImpl.createPartnerRoleChannel(BindingContextImpl.java:101) >> at >> org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.doHydrate(BpelProcess.java:868) >> at >> org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.access$100(BpelProcess.java:777) >> >> I have attached the complete log files along with other files as well. >> Please let me know how do I resolve this problem. >> >> Thanks, >> Vikas >> >> -----Original Message----- >> From: Tammo van Lessen [mailto:[email protected]] >> Sent: Thursday, March 25, 2010 8:21 PM >> To: [email protected] >> Subject: Re: Issue with deploying BPEL process into Apache ODE >> >> Hi, >> >> >> Garg, Vikas wrote: >>> “FATAL - GeronimoLog.fatal(116) | openResource: invalid scheme (should >>> be urn:) D:/vikas/TestBPELWS/SampleWS/WebContent/wsdl/SampleHelloWS.wsdl” >> The location attribute for the import in CallerArtifacts.wsdl must point to >> a URL, so you'd need to add a file:// before the path. >> >> HTH, >> Tammo >> >> -- >> Tammo van Lessen - http://www.taval.de > > -- Tammo van Lessen - http://www.taval.de
