Hi, I am trying to call web service through Appian function webservic

sunnya over 10 years ago

Hi,

I am trying to call web service through Appian function webservicequery below is my sample code webservicequery(
a!wsConfig(
wsdlUrl: "localhost:8182/.../MailService
service: "{localhost:8182/}MailService",
port: "MailServiceSOAP",
operation: "{localhost:8182/}MailOperation"
),
{
CreateUrlSoapIn: {
real_url: "a@gmail.com~hi~test"
}
}
)

This is a java web service and ~ is the tokenizer used in java code

but it gives the following error
aused by: com.appiancorp.ws.exception.UnsupportedWSDLException: The WSDL cannot be processed. It contains invalid or unsupported elements. Details: Service {localhost:8182/}MailService was not found in the WSDL (APNX-1-4043-001)

I have tried calling it through Appian Smart service its working fine there but in function its giving the above error. It will be great if anybody could help me in this. Thanks in A...

Discussion posts and replies are publicly visible

0 sunnya over 10 years ago

...dvance
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

It seems a problem with the service name. Can you attach your wsdl?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sunnya over 10 years ago

HI Eduardo,

<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="MailService" targetNamespace="www.example.org/.../" xmlns:wsdl="schemas.xmlsoap.org/.../" xmlns:tns="www.example.org/.../" xmlns:xsd="www.w3.org/.../XMLSchema" xmlns:soap="schemas.xmlsoap.org/.../">
- <wsdl:types>
- <xsd:schema targetNamespace="www.example.org/.../">
- <xsd:element name="MailServiceOperation">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="MailData" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="MailServiceOperationResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="out" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="MailServiceOperationResponse">
<wsdl:part name="parameters" element="tns:MailServiceOperationResponse" />
</wsdl:message>
- <wsdl:message name="MailServiceOperationRequest">
<wsdl:part name="parameters" element="tns:MailServiceOperation" />
</wsdl:message>
- <wsdl:portType name="MailService">
- <wsdl:operation name="MailOperation">
<wsdl:input message="tns:MailServiceOperationRequest" />
<wsdl:output message="tns:MailServiceOperationResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="MailServiceSOAP" type="tns:MailService">
<soap:binding style="document" transport="schemas.xmlsoap.org/.../http" />
- <wsdl:operation name="MailOperation">
<soap:operation soapAction="www.example.org/.../MailServiceOperation" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="MailService">
- <wsdl:port name="MailServiceSOAP" binding="tns:MailServiceSOAP">
<soap:address location="localhost:8182/.../" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sunnya over 10 years ago

this is my wsdl for your reference its working fine with call web service smart service
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike James
Certified Lead Developer
over 9 years ago

was there any resolution to this? - having similar issue
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel