Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » BPEL Designer » PartnerLink - Wrong WSDL-Format?
PartnerLink - Wrong WSDL-Format? [message #544443] Fri, 02 July 2010 16:45
DrCastle is currently offline DrCastleFriend
Messages: 1
Registered: July 2010
Junior Member
Hello Community,

I searched through the existing threads and I think my problem is of some other kind than the partner link problems in this forum.

I'm using Eclipse 3.4, Tomcat 6.0.26, Ode 1.3.4 and Axis 2 1.5.1with the BPEL Designer 0.4.0.

When I try to add a WSDL definition to a partner link, the Designer can't load the WSDL file. I remember that I was once able to load a wsdl file that I accidentaly created when using axis 1, but I don't know how to use axis 1 in my IDE...

Are the components listed above even compatible?

Here is an example of a WSDL file a published web service running on the tomcat server:

<wsdl:definitions targetNamespace="http://studienarbeit.mab">
<wsdl:documentation>
		Please Type your service description here
	</wsdl:documentation>
−
<wsdl:types>
−
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://studienarbeit.mab">
−
<xs:element name="setzeEmailAdresse">
−
<xs:complexType>
−
<xs:sequence>
<xs:element minOccurs="0" name="pSSOID" type="xs:int"/>
<xs:element minOccurs="0" name="pAdresse" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
<xs:element name="neuerMitarbeiter">
−
<xs:complexType>
−
<xs:sequence>
<xs:element minOccurs="0" name="vorname" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="nachname" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="titel" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="berufsBez" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="anschrift" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="plz" type="xs:int"/>
<xs:element minOccurs="0" name="wohnort" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="gebDat" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="bruttoGehalt" type="xs:int"/>
<xs:element minOccurs="0" name="sozNr" type="xs:int"/>
<xs:element minOccurs="0" name="dienstwagen" type="xs:boolean"/>
<xs:element minOccurs="0" name="visitenkarte" type="xs:boolean"/>
<xs:element minOccurs="0" name="emailVorgesetzter" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="backgroundDaten" nillable="true" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
<xs:element name="neuerMitarbeiterResponse">
−
<xs:complexType>
−
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:int"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
<xs:element name="erstelleEinstellungsbericht">
−
<xs:complexType>
−
<xs:sequence>
<xs:element minOccurs="0" name="pSSOID" type="xs:int"/>
<xs:element minOccurs="0" name="pZusaetzlicheDaten" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
−
<xs:element name="erstelleEinstellungsberichtResponse">
−
<xs:complexType>
−
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
−
<wsdl:message name="erstelleEinstellungsberichtRequest">
<wsdl:part name="parameters" element="ns:erstelleEinstellungsbericht"/>
</wsdl:message>
−
<wsdl:message name="erstelleEinstellungsberichtResponse">
<wsdl:part name="parameters" element="ns:erstelleEinstellungsberichtResponse"/>
</wsdl:message>
−
<wsdl:message name="neuerMitarbeiterRequest">
<wsdl:part name="parameters" element="ns:neuerMitarbeiter"/>
</wsdl:message>
−
<wsdl:message name="neuerMitarbeiterResponse">
<wsdl:part name="parameters" element="ns:neuerMitarbeiterResponse"/>
</wsdl:message>
−
<wsdl:message name="setzeEmailAdresseRequest">
<wsdl:part name="parameters" element="ns:setzeEmailAdresse"/>
</wsdl:message>
−
<wsdl:portType name="ERPServicePortType">
−
<wsdl:operation name="erstelleEinstellungsbericht">
<wsdl:input message="ns:erstelleEinstellungsberichtRequest" wsaw:Action="urn:erstelleEinstellungsbericht"/>
<wsdl:output message="ns:erstelleEinstellungsberichtResponse" wsaw:Action="urn:erstelleEinstellungsberichtResponse"/>
</wsdl:operation>
−
<wsdl:operation name="neuerMitarbeiter">
<wsdl:input message="ns:neuerMitarbeiterRequest" wsaw:Action="urn:neuerMitarbeiter"/>
<wsdl:output message="ns:neuerMitarbeiterResponse" wsaw:Action="urn:neuerMitarbeiterResponse"/>
</wsdl:operation>
−
<wsdl:operation name="setzeEmailAdresse">
<wsdl:input message="ns:setzeEmailAdresseRequest" wsaw:Action="urn:setzeEmailAdresse"/>
</wsdl:operation>
</wsdl:portType>
−
<wsdl:binding name="ERPServiceSoap11Binding" type="ns:ERPServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
−
<wsdl:operation name="erstelleEinstellungsbericht">
<soap:operation soapAction="urn:erstelleEinstellungsbericht" style="document"/>
−
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
−
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="neuerMitarbeiter">
<soap:operation soapAction="urn:neuerMitarbeiter" style="document"/>
−
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
−
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="setzeEmailAdresse">
<soap:operation soapAction="urn:setzeEmailAdresse" style="document"/>
−
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
−
<wsdl:binding name="ERPServiceSoap12Binding" type="ns:ERPServicePortType">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
−
<wsdl:operation name="erstelleEinstellungsbericht">
<soap12:operation soapAction="urn:erstelleEinstellungsbericht" style="document"/>
−
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
−
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="neuerMitarbeiter">
<soap12:operation soapAction="urn:neuerMitarbeiter" style="document"/>
−
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
−
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="setzeEmailAdresse">
<soap12:operation soapAction="urn:setzeEmailAdresse" style="document"/>
−
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
−
<wsdl:binding name="ERPServiceHttpBinding" type="ns:ERPServicePortType">
<http:binding verb="POST"/>
−
<wsdl:operation name="erstelleEinstellungsbericht">
<http:operation location="ERPService/erstelleEinstellungsbericht"/>
−
<wsdl:input>
<mime:content type="text/xml" part="erstelleEinstellungsbericht"/>
</wsdl:input>
−
<wsdl:output>
<mime:content type="text/xml" part="erstelleEinstellungsbericht"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="neuerMitarbeiter">
<http:operation location="ERPService/neuerMitarbeiter"/>
−
<wsdl:input>
<mime:content type="text/xml" part="neuerMitarbeiter"/>
</wsdl:input>
−
<wsdl:output>
<mime:content type="text/xml" part="neuerMitarbeiter"/>
</wsdl:output>
</wsdl:operation>
−
<wsdl:operation name="setzeEmailAdresse">
<http:operation location="ERPService/setzeEmailAdresse"/>
−
<wsdl:input>
<mime:content type="text/xml" part="setzeEmailAdresse"/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
−
<wsdl:service name="ERPService">
−
<wsdl:port name="ERPServiceHttpSoap11Endpoint" binding="ns:ERPServiceSoap11Binding">
<soap:address location="http://localhost:8080/Dienste/services/ERPService.ERPServiceHttpSoap11Endpoint/"/>
</wsdl:port>
−
<wsdl:port name="ERPServiceHttpSoap12Endpoint" binding="ns:ERPServiceSoap12Binding">
<soap12:address location="http://localhost:8080/Dienste/services/ERPService.ERPServiceHttpSoap12Endpoint/"/>
</wsdl:port>
−
<wsdl:port name="ERPServiceHttpEndpoint" binding="ns:ERPServiceHttpBinding">
<http:address location="http://localhost:8080/Dienste/services/ERPService.ERPServiceHttpEndpoint/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>


Best regards
DrCastle

edit: I'm not sure, but this seems to be wsdl 2.0, does the bpel-designer only support 1.1?

[Updated on: Fri, 02 July 2010 17:08]

Report message to a moderator

Previous Topic:Editing deploy.xml Cause org.eclipse.jface and java.lang.LinkageError and javax/wsdl/Binding problem
Next Topic:help on creating bpel files
Goto Forum:
  


Current Time: Fri Dec 19 07:22:37 GMT 2014

Powered by FUDForum. Page generated in 0.03232 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software