Hi Les, Can you verify with the patch attached in https://issues.apache.org/jira/browse/ODE-1013
Let me know if this works. regards, sathwik On Thu, Nov 14, 2013 at 9:43 AM, Sathwik B P <[email protected]> wrote: > Hi Les, > > I deployed both your processes on tomcat-7.0.42, ode-1.3.6, mysql-5.5. > Below is the endpoints displayed on the deployments page ( > http://localhost:8080/ode/deployment/services/) > > > <http://localhost:8080/ode/deployment/bundles/ExternalHelloWorld/ExternalHelloWorld.wsdl> > > ExternalHelloWorld<http://localhost:8080/ode/deployment/bundles/ExternalHelloWorld/ExternalHelloWorld.wsdl> > > - Axis2 WSDL: > http://localhost:8080/ode/processes/ExternalHelloWorld?wsdl > - Endpoint: http://localhost:8080/ode/processes/ExternalHelloWorld > - Operations: process > > HelloWorld<http://localhost:8080/ode/deployment/bundles/HelloWorld/imports/ExternalHelloWorld.wsdl> > > - Axis2 WSDL: http://localhost:8080/ode/processes/HelloWorld?wsdl > - Endpoint: http://localhost:8080/ode/processes/HelloWorld > - Operations: process > > > I see the problem what you are experiencing, the context/service path > (ode/processes) is completely missing in the endpoint address though it did > not happen the first time when I imported the wsdl into soapui. > Will investigate and let you know. Thanks for reporting the problem. > > *We always recommend to use the endpoint for each of the deployed process > displayed on the deployments page.* > > FYI: Axis 2 appends the port name to the end of the service endpoint when > the wsdl is dynamically generated by it, and hence you see HelloWorldPort > appended > http://localhost:8080//HelloWorld.HelloWorldPort/<http://localhost:8080/HelloWorld.HelloWorldPort/> > > regards, > sathwik > > > > > regards, > asthwik > > > On Wed, Nov 13, 2013 at 10:08 PM, Les Spivey <[email protected]>wrote: > >> Hello All. >> >> >> >> I am running Ode 1.3.6 in Tomcat 7.0.26. I have deployed two BPEL >> processes (attached). HelloWorld calls ExternalHelloWorld. I create a >> SoapUI project using this url to the HelloWorld process: >> http://localhost:8080/ode/services/HelloWorld?wsdl. This is the >> endpoint url in the wsdl: >> http://localhost:8080/ode/processes/HelloWorld.HelloWorldPort/. This >> project executes correctly. However, when I create a second project using >> the same url to the HelloWorld process as before - >> http://localhost:8080/ode/processes/HelloWorld.HelloWorldPort/, the >> endpoint url looks like: >> http://localhost:8080//HelloWorld.HelloWorldPort/<http://localhost:8080/HelloWorld.HelloWorldPort/>. >> Notice that "ode/processes" is now missing from the endpoint url. The >> second process will not execute properly. Moreover, once this happens, >> "ode/processes" will be missing from the endpoint of all deployed >> processes. Everything seems to work fine until a deployed BPEL process >> calls an external web service. After that the soap:address location in the >> service wsdl will be incorrect. Projects are attached. I did try >> accessing the deployed processes using >> http://localhost:8080/ode/deployment/services as an earlier email >> suggested but this gives me the wrong wsdl. >> >> >> >> The scenario I described above does work in Ode 1.3.5. I do notice that, >> in Ode 1.3.5, the wsdl generated for a deployed process contains 3 bindings >> - SOAP11, SOAP12, and HTTP. There is only one binding in the wsdl >> generated for a deployed process in Ode 1.3.6. I have not changed any >> configuration files in Ode 1.3.6. Thanks in advance for any suggestions on >> what may be causing this problem. >> > >
