GlobalPartnerLink - don't see all WSDLs

[izgur]

Hey, i copied some WSDLs to my BPEL project to the bpelContent.

Then I made a BPEL process file, added an INVOKE element and started to make the globalPartnerLink. I don't see all WSDLs. I think I don't see the ones deployed with Axis2. Why not?

What could be wrong with this WSDL:

<?xml version="1.0" encoding="utf-8" ?>
<definitions name="TransactionsService"
                targetNamespace="http://transactions"
                xmlns='http://schemas.xmlsoap.org/wsdl/'
             xmlns:wsdl='http://schemas.xmlsoap.org/wsdl'
             xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
             xmlns:wsdlsoap='http://schemas.xmlsoap.org/wsdl/soap'
             xmlns:xs='http://www.w3.org/2001/XMLSchema'
             xmlns:tns='http://transactions' >

<wsdl:types>

<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://transactions">

<xs:element name="getTransactionID">

<xs:complexType>

<xs:sequence>
<xs:element minOccurs="0" name="args0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="args1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>

<xs:element name="getTransactionIDResponse">

<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="getTransactionIDRequest">
<wsdl:part name="parameters" element="ns:getTransactionID"/>
</wsdl:message>

<wsdl:message name="getTransactionIDResponse">
<wsdl:part name="parameters" element="ns:getTransactionIDResponse"/>
</wsdl:message>

<wsdl:portType name="TransactionsServicePortType">

<wsdl:operation name="getTransactionID">
<wsdl:input message="ns:getTransactionIDRequest"/>
<wsdl:output message="ns:getTransactionIDResponse"/>
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="TransactionsServiceSoap11Binding" type="ns:TransactionsServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>

<wsdl:operation name="getTransactionID">
<soap:operation soapAction="urn:getTransactionID" 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="TransactionsService">

<wsdl:port name="TransactionsServiceHttpSoap11Endpoint" binding="ns:TransactionsServiceSoap11Binding">
<soap:address location="http://127.0.0.1:9000/axis2/services/TransactionsService.TransactionsServiceHttpSoap11Endpoint/"/>
</wsdl:port>

</wsdl:service>
</definitions>

Any idea?

[izgur]

got it to work...

erase wsdl: prefixes.

add  xmlns:tns='http://transactions' to <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://transactions">

change ns prefixes to tns

That was all

[bbrodt]

Hi Igor,

Looks like the "wsdl" prefix not being recognized is a bug in the BPEL editor - can you please create a JIRA for Project="Tools (JBoss Tools)", Component="bpel", Fix Version="3.2.0.CR1" and then assign it to me (Robert Brodt).

The "change ns prefixes to tns" looks like a problem with who/whatever created the WSDL since the "ns" prefix is not defined anywhere.

Thanks!

[izgur]

You were right about the ns - tns problem. I can't believe I didn't see that...

I got one more question, which can be posted here...   Has RiftSaw problems with arrays ???

I made a getArray and setArray WS just to be sure it(BPEL) will work, when i got to call it..

I imported the wsdl, wrote the partner link in the imported WSDL and the BPEL file.

The made partnerlink shows up, but doesn't have any methods, so it's useless.

The same service without the arrays works well...

[objectiser]

Not sure - we keep meaning to write an example using arrays (see https://issues.jboss.org/browse/RIFTSAW-219), but haven't had time to try it yet, and there does not seem to be any such examples anywhere.

You could try running your example on ODE in tomcat, to see if it has the same problem - if not, then it would be a riftsaw problem.

Regards

Gary