ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Łukasz Budnik" <lukasz.bud...@gmail.com>
Subject Re: deploy.xml - Cannot find definition for service error
Date Thu, 24 Jan 2008 21:54:02 GMT
Hi Alex,

By Java class is very simple:

package org.xh.nuntius.sandbox.tomcat.ws;

public class TimerService {
	
	public long getTimestamp() {
		return System.currentTimeMillis();
	}

}

it is deployed as AAR (exported using axis2-eclipse-service-archiver-wizard).

And the WSDL is automatically generated by Axis2 and is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://org.apache.axis2/xsd"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:ns0="http://ws.tomcat.sandbox.nuntius.xh.org"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
targetNamespace="http://ws.tomcat.sandbox.nuntius.xh.org">
    <wsdl:documentation>TimerService</wsdl:documentation>
    <wsdl:types>
        <xs:schema xmlns:ns="http://ws.tomcat.sandbox.nuntius.xh.org"
attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://ws.tomcat.sandbox.nuntius.xh.org">
            <xs:element name="getTimestampResponse">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="return" type="xs:long"/>

                    </xs:sequence>
                </xs:complexType>
            </xs:element>
        </xs:schema>
    </wsdl:types>
    <wsdl:message name="getTimestampRequest"/>
    <wsdl:message name="getTimestampResponse">
        <wsdl:part name="parameters" element="ns0:getTimestampResponse"/>
    </wsdl:message>

    <wsdl:portType name="TimerServicePortType">
        <wsdl:operation name="getTimestamp">
            <wsdl:input message="ns0:getTimestampRequest"
wsaw:Action="urn:getTimestamp"/>
            <wsdl:output message="ns0:getTimestampResponse"
wsaw:Action="urn:getTimestampResponse"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="TimerServiceSOAP11Binding"
type="ns0:TimerServicePortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document"/>
        <wsdl:operation name="getTimestamp">

            <soap:operation soapAction="urn:getTimestamp" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>

    <wsdl:binding name="TimerServiceSOAP12Binding"
type="ns0:TimerServicePortType">
        <soap12:binding
transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="getTimestamp">
            <soap12:operation soapAction="urn:getTimestamp" style="document"/>
            <wsdl:input>
                <soap12:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap12:body use="literal"/>

            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="TimerServiceHttpBinding"
type="ns0:TimerServicePortType">
        <http:binding verb="POST"/>
        <wsdl:operation name="getTimestamp">
            <http:operation location="TimerService/getTimestamp"/>
            <wsdl:input>
                <mime:content type="text/xml" part="getTimestamp"/>

            </wsdl:input>
            <wsdl:output>
                <mime:content type="text/xml" part="getTimestamp"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="TimerService">
        <wsdl:port name="TimerServiceSOAP11port_http"
binding="ns0:TimerServiceSOAP11Binding">
            <soap:address
location="http://localhost:8080/axis2/services/TimerService"/>

        </wsdl:port>
        <wsdl:port name="TimerServiceSOAP12port_http"
binding="ns0:TimerServiceSOAP12Binding">
            <soap12:address
location="http://localhost:8080/axis2/services/TimerService"/>
        </wsdl:port>
        <wsdl:port name="TimerServiceHttpport"
binding="ns0:TimerServiceHttpBinding">
            <http:address
location="http://localhost:8080/axis2/services/TimerService"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>

best regards
Łukasz

On 24/01/2008, Alex Boisvert <boisvert@intalio.com> wrote:
> Hi Lukasz,
>
> Can you send your TimerService.wsdl for inspection?
>
> alex
>
>
> On 1/24/08, Łukasz Budnik <lukasz.budnik@gmail.com> wrote:
> >
> > Hi All!
> >
> > I have a very strange error during deployment of new process, here is
> > the root cause:
> >
> > org.apache.ode.bpel.iapi.ContextException: Cannot find definition for
> > service {h
> > ttp://ws.tomcat.sandbox.nuntius.xh.org}TimerService in the context of
> > process {ht
> > tp://bpel.ode.sandbox.nuntius.xh.org}OdeTest2-25
> >
> > I have a very simple TimerService deployed in AXIS2
> > (http://localhost:8080/axis2/services/TimerService), its namespace is:
> >
> > http://ws.tomcat.sandbox.nuntius.xh.org
> >
> > Now, I'm deploying Ode process called OdeTest2, that invokes TimerService.
> >
> > Its namespace is:
> >
> > http://bpel.ode.sandbox.nuntius.xh.org
> >
> > my deploy.xml descriptor is as follows:
> >
> > <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
> >         xmlns:tns="http://bpel.ode.sandbox.nuntius.xh.org"
> >         xmlns:ns="http://ws.tomcat.sandbox.nuntius.xh.org">
> >         <process name="tns:OdeTest2">
> >                 <active>true</active>
> >                 <provide partnerLink="client">
> >                         <service name="tns:OdeTest2Service"
> > port="OdeTest2Port" />
> >                 </provide>
> >                 <invoke partnerLink="TimerPartnerLink">
> >                         <service name="ns:TimerService"
> >                                 port="TimerServiceSOAP12port_http" />
> >                 </invoke>
> >         </process>
> > </deploy>
> >
> > I'm loosing my mind, I saw Sebastien Mosser thread about the very same
> > problem,
> > his solution was very simple - he had different namespaces used.
> > (vide
> > http://mail-archives.apache.org/mod_mbox/ode-user/200712.mbox/%3c5582dd3b0712031033q351313fn6cf2e967486e271@mail.gmail.com%3e
> > )
> >
> > But I have only one web service. There cannot be any error...
> >
> > or is it?
> >
> > any piece of advice is highly appreciated ;)
> >
> > best regards
> > Łukasz
> >
>
Mime
View raw message