ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris <dch...@gmail.com>
Subject Re: Unable to access WSDL definition to activate MyRole endpoint
Date Tue, 02 Oct 2007 13:29:44 GMT
I switched to types and now I get this error:
15:23:50,568 ERROR [DeploymentPoller] Deployment of RandomColor failed,
aborting for now.
org.apache.ode.bpel.iapi.ContextException: Deploy failed; error:
[CompilationErrors] Compilation completed with 6 error(s):
  file:/home/chris/devel/SeT/apache-tomcat-5.5.25/webapps/ode/WEB-INF/processes/RandomColor/RandomColor.bpel:19:
error: [UndeclaredXsdType] Attempt to reference undecla
red XSD type "{http://schemas.xmlsoap.org/wsdl/}string".
  file:/home/chris/devel/SeT/apache-tomcat-5.5.25/webapps/ode/WEB-INF/processes/RandomColor/RandomColor.bpel:20:
error: [UndeclaredXsdType] Attempt to reference undecla
red XSD type "{http://schemas.xmlsoap.org/wsdl/}string".

Here is my wsdl file (I tried both rpc:literal and document:literal, none is
working : same error):
<?xml version="1.0"?>
<definitions name="RandomColor"
        targetNamespace="http://sample.bpel.org/bpel/sample"
        xmlns:tns="http://sample.bpel.org/bpel/sample"
        xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
        xmlns="http://schemas.xmlsoap.org/wsdl/"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">


<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
    <message name="RandomColorRequestMessage">
        <part name="payload" type="string"/>
    </message>
    <message name="RandomColorResponseMessage">
        <part name="payload" type="string"/>
    </message>

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PORT TYPE DEFINITION - A port type groups a set of operations into
     a logical service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->

    <!-- portType implemented by the RandomColor BPEL process -->
    <portType name="RandomColor">
        <operation name="getRandomColor">
            <input  message="tns:RandomColorRequestMessage" />
            <output message="tns:RandomColorResponseMessage"/>
        </operation>
    </portType>


<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
    <plnk:partnerLinkType name="RandomColor">
        <plnk:role name="RandomColorProvider" portType="tns:RandomColor"/>
    </plnk:partnerLinkType>

    <binding name="RandomColorBinding" type="tns:RandomColor">
        <soap:binding style="document"
            transport="http://schemas.xmlsoap.org/soap/http" />
        <operation name="getRandomColor">
            <soap:operation
                soapAction="
http://sample.bpel.org/bpel/sample/getRandomColor" />
            <input>
                <soap:body use="literal" />
            </input>
            <output>
                <soap:body use="literal" />
            </output>
        </operation>
    </binding>
    <service name="RandomColorService">
        <port name="RandomColorPort" binding="tns:RandomColorBinding">
            <soap:address location="
http://localhost:8080/ode/processes/RandomColorService"></soap:address>
        </port>
    </service>
</definitions>

Here are the lines with errors in BPEL:
    <bpws:variables>
        <bpws:variable messageType="tns:RandomColorRequestMessage"
name="input"/>
        <bpws:variable messageType="tns:RandomColorResponseMessage"
name="output"/>

What did I do wrong?

Thanks,

On 10/2/07, Alex Boisvert <boisvert@intalio.com> wrote:
>
> On 10/2/07, Chris <dchris@gmail.com> wrote:
> >
> > Thanks. Looks like it found the WSDL now but it fails later:
> >
> > 15:05:14,892 ERROR [DeploymentPoller] Deployment of RandomColor failed,
> > aborting for now.
> > org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint
> for
> > service {http://sample.bpel.org/bpel/sample}RandomColorService and port
> > RandomColorPort
> > ...
>
>
> Caused by:
> >
> >
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:RPC-literal
> > type message part payload should have a type attribute
>
>
> However, I have types string for input and output in the wsdl. Note: The
> > wsdl was generated with Eclipse BPEL editor.
> >
> >
> Per WS-I BasicProfile 1.1, if you use RPC-Literal, all your message parts
> need to be xsd:types (not elements).
>
> You can change your message parts, or you can change the style to
> Doc-Literal if you have only one message body part.  Either way, it sounds
> like you'll need to tweak the WSDL to make it WS-I BasicProfile
> 1.1compliant.  If you are familiar with SOAPUI, you can use it to
> validate for
> compliance.
>
> cheers,
> alex
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message