3 Replies Latest reply on Apr 19, 2010 8:44 AM by rebody

    jBPM BPEL & Eclipse Process Designer

      HI, I get an exception when I try to deploy a BPEL file generated by aid of the Eclipse BPEL Designer.

       

      I'm using following versions:

       

      JBoss 4.2.0.GA

      JBPM BPEL 1.1.1

      BPEL Editor 0.4.0

       

      Exception.jpg

      The corresponding section of the BPEL file:

       

      [...]

       

      <!-- Import the client WSDL -->
          <bpel:import location="DBTestArtifacts.wsdl" namespace="http://eclipse.org/bpel/sample"
                  importType="http://schemas.xmlsoap.org/wsdl/" />
              
          <!-- ================================================================= -->        
          <!-- PARTNERLINKS                                                      -->
          <!-- List of services participating in this BPEL process               -->
          <!-- ================================================================= -->        
          <bpel:partnerLinks>
              <!-- The 'client' role represents the requester of this service. -->
              <bpel:partnerLink name="client"
                           partnerLinkType="tns:DBTest"
                           myRole="DBTestProvider"
                           />
             
              <bpel:partnerLink name="DBServ" partnerLinkType="tns:DBServT" partnerRole="DBServType"></bpel:partnerLink>
          </bpel:partnerLinks>

       

      [...]

       

       

      I would be very thankful for any suggestions!

       

      Best regards,

      Annette

        • 1. Re: jBPM BPEL & Eclipse Process Designer
          rebody

          Hi Annette,

            It seems that BPEL cannot find the qualify name of WSDL. Would you mind show me the related WSDL file ?

          • 2. Re: jBPM BPEL & Eclipse Process Designer

            Hi Huisheng,

             

            here the wsdl of the BPEL process:

             

             

             

            <?xml version="1.0" encoding="UTF-8" standalone="no"?>
            <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://eclipse.org/bpel/sample" xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop" xmlns:wsdl="http://microsoft.com/webservices/" name="DBTest" targetNamespace="http://eclipse.org/bpel/sample">

             

            <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 TYPE DEFINITION - List of types participating in this BPEL process
                 The BPEL Designer will generate default request and response types
                 but you can define or import any XML Schema type and use them as part
                 of the message types.
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->   
                <plnk:partnerLinkType name="DBServT">
                <plnk:role name="DBServType">
                <plnk:portType name="wsdl:DBServiceSoap"/>
                </plnk:role>
                </plnk:partnerLinkType>
                <import location="interface/DBService.wsdl" namespace="http://microsoft.com/webservices/"/>

             

                <types>
                    <schema xmlns="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://eclipse.org/bpel/sample">

             

                        <element name="DBTestRequest">
                            <complexType>
                                <sequence>
                                    <element name="input" type="string"/>
                                </sequence>
                            </complexType>
                        </element>

             

                        <element name="DBTestResponse">
                            <complexType>
                                <sequence>
                                    <element name="result" type="string"/>
                                </sequence>
                            </complexType>
                        </element>
                    </schema>
                </types>

             


            <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 MESSAGE TYPE DEFINITION - Definition of the message types used as
                 part of the port type defintions
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->   
                <message name="DBTestRequestMessage">
                    <part element="tns:DBTestRequest" name="payload"/>
                </message>
                <message name="DBTestResponseMessage">
                    <part element="tns:DBTestResponse" name="payload"/>
                </message>

             

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

             

                <!-- portType implemented by the DBTest BPEL process -->
                <portType name="DBTest">
                    <operation name="process">
                        <input message="tns:DBTestRequestMessage"/>
                        <output message="tns:DBTestResponseMessage"/>
                    </operation>
                </portType>

             

            <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 PARTNER LINK TYPE DEFINITION
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->   
                <plnk:partnerLinkType name="DBTest">
                    <plnk:role name="DBTestProvider" portType="tns:DBTest"/>
                </plnk:partnerLinkType>
            </definitions>

             

             

             

            and the wsdl of the partner link:

             

             

             

            <?xml version="1.0" encoding="UTF-8"?>
            <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://microsoft.com/webservices/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://microsoft.com/webservices/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
              <wsdl:types>
                <s:schema elementFormDefault="qualified" targetNamespace="http://microsoft.com/webservices/">
                  <s:element name="get_CAX_Query">
                    <s:complexType>
                      ...
                    </s:complexType>
                  </s:element>
                   <s:complexType name="ArrayOfResult">
                    <s:sequence>
                      <s:element minOccurs="0" maxOccurs="unbounded" name="Result" type="tns:Result"/>
                    </s:sequence>
                  </s:complexType>
                  <s:complexType name="Result">
                    ........
                    <s:sequence>
                    </s:sequence>
                  </s:complexType>
                    ...........
                </s:complexType>
              <wsdl:portType>
                <wsdl:operation name="get_CAX_Query">
                  <wsdl:input message="tns:get_CAX_QuerySoapIn"/>
                  <wsdl:output message="tns:get_CAX_QuerySoapOut"/>
                </wsdl:operation>
              </wsdl:portType>
              <wsdl:binding name="DBServiceSoap" type="tns:DBServiceSoap">
                <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
                 <wsdl:operation name="get_CAX_Query">
                  <soap:operation soapAction="http://microsoft.com/webservices/get_CAX_Query" style="document"/>
                  <wsdl:input>
                    <soap:body use="literal"/>
                  </wsdl:input>
                  <wsdl:output>
                    <soap:body use="literal"/>
                  </wsdl:output>
                </wsdl:operation>
              </wsdl:binding>
               <wsdl:service name="DBService">
                <wsdl:port name="DBServiceSoap" binding="tns:DBServiceSoap">
                  <soap:address location="http://localhost/DBWS/DBService.asmx"/>
                </wsdl:port>
              </wsdl:service>
            </wsdl:definitions>

             

             

             

             

             

            Regards,

            Annette

            • 3. Re: jBPM BPEL & Eclipse Process Designer
              rebody

              Hi Annette,

                I cannot find the related portType for partnerLink "<plnk:partnerLinkType name="DBServT">", So I think it would be the cause of Exception.