soap-proxy and service proxy errors

resp...@gmail.com

unread,

Feb 18, 2015, 7:26:45 PM2/18/15

to membrane...@googlegroups.com

Hi MemBrane, I'm Gary from Apex.NC,USA. I hope everyone there is doing great.

You have a very nice product i installed 4.18 and the samples worked well and i created my own sample that also was a breeze. I too have problems with maven build.

I'm trying to use the Membrane to connect to a server. I have soapui requests that works fine going directly to a server but errors in both service-proxy and soap-proxy.

1). is there an xml config statement for both service-proxy and soap-proxy without checking the wsdl and with doing any transforms?

- since it works without membrane, i'm guessing the service proxy must be changing something.

- I get an explicit error from Membrane in Soap proxy because it can't reach something in the wsdl. Is there a way to tell soap-proxy not to validate wsdl url/uri?

-- basically the wsdl intentionally has markup to url's that aren't there.

2). Ultimately if would like to route based on x-path but in my simple hello world soapproxy it doesn't work. Thise is what i coded.

</switch>

</soapProxy>

3). I too have had build problems with 4.18 due to a few artifacts

4). The developer.md says to import to:

3. In the next section you will have to set the service-proxy\cli directory as root-directory.

should it not be service-proxy?

Then all the projects are there including service-proxy-annot . If I do service-proxy\cli then i can't see any other projects.

Thank you in advance, and this is an awesome product!

Gary

Thomas Bayer

unread,

Feb 19, 2015, 4:40:38 AM2/19/15

to membrane...@googlegroups.com

Hi Gary,

Am 19.02.15 um 01:26 schrieb resp...@gmail.com:

Hi MemBrane, I'm Gary from Apex.NC,USA. I hope everyone there is doing great.

We are good. Thx.

You have a very nice product i installed 4.18 and the samples worked well and i created my own sample that also was a breeze. I too have problems with maven build.

I'm trying to use the Membrane to connect to a server. I have soapui requests that works fine going directly to a server but errors in both service-proxy and soap-proxy.

1). is there an xml config statement for both service-proxy and soap-proxy without checking the wsdl and with doing any transforms?

- since it works without membrane, i'm guessing the service proxy must be changing something.

- I get an explicit error from Membrane in Soap proxy because it can't reach something in the wsdl. Is there a way to tell soap-proxy not to validate wsdl url/uri?

-- basically the wsdl intentionally has markup to url's that aren't there.

As already written. The WSDL would be helpful.

2). Ultimately if would like to route based on x-path but in my simple hello world soapproxy it doesn't work. Thise is what i coded.

<soapProxy port="2001" wsdl="http://localhost:8090/?wsdl">

<log level="TRACE" />

<switch>

<case xPath="hel:sayHello[.=1]" url="http://localhost:8080/WebService/services/HelloWorld" />

<case xPath="hel:sayHello[.=2]" url="http://localhost:8090/WebService/services/HelloWorld" />

</switch>

</soapProxy>

Can you post the entire proxies.xml. Seems like you have namespace issues.

3). I too have had build problems with 4.18 due to a few artifacts

4). The developer.md says to import to:

3. In the next section you will have to set the service-proxy\cli directory as root-directory.

should it not be service-proxy?

Then all the projects are there including service-proxy-annot . If I do service-proxy\cli then i can't see any other projects.

We will have a look at the build. Thanks.

Cheers,
Thomas

Gary W

unread,

Feb 19, 2015, 12:09:55 PM2/19/15

to membrane...@googlegroups.com

Hi Thomas, Thank you for the fast reply.

More info below.

For service-proxy which doesn't have wsdl. Please keep in mind in soapui direct to the service everything works fine. I'm hoping for a config solution, because server team says it's working fine. We don't require any transforms or any validation. long term we only need xpath routeing to different targets.

<ERROR_CODE>1002</ERROR_CODE>

<ERROR_TEXT>Not a valid root tag</ERROR_TEXT>

<SEVERITY>FATAL</SEVERITY>

</STATUS>

</configuration>

For soap-proxy port 2017

<html>

<head>

<title>Bad Gateway</title>

</head>

<body>

<h1>Bad Gateway</h1>

<p>Target http://internalName:9018/eDBInBoundCSD/eDBInBoundCSDServices is not reachable.</p>

</body>

</html>

For soap-proxy 2018

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Body>

<soapenv:Fault>

<faultcode>soapenv:Server</faultcode>

<faultstring>Message validation failed!</faultstring>

<detail>Validation failed: org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 110; cvc-elt.1: Cannot find the declaration of element 'INBOUND_GET_SERVICE_REQUESTS'.;</detail>

</soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

Here is proxy.xml

<spring:beans xmlns="http://membrane-soa.org/proxies/1/"

xmlns:spring="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

http://membrane-soa.org/proxies/1/ http://membrane-soa.org/schemas/proxies-1.xsd">

</soapProxy>

</switch>

</soapProxy>

</serviceProxy>

</serviceProxy>

</soapProxy>

<validator

wsdl="http://internalName.com:8888/eDBInBoundCSD/eDBInBoundCSD.wsdl"

skipFaults="true" />

</soapProxy>

</basicAuthentication>

</serviceProxy>

</router>

</spring:beans>

WSDL

<?xml version="1.0"?>

<definitions name="eDBInBoundCSDServices"

targetNamespace="http://AppName.internalName.com/ns/edb/wsdl/eDBInBoundCSD/2003-08"

xmlns:tns="http://AppName.internalName.com/ns/edb/wsdl/eDBInBoundCSD/2003-08"

xmlns:edbs="http://AppName.internalName.com/ns/edb/services/eDBInBoundCSDServices/2003-08"

xmlns:sr="http://xmlns.internalName.com/SIPD/eDBInBoundCSD/2013/02/ServiceRequests"

xmlns:fbc="http://AppName.internalName.com/ns/fbc/messages/2003-08"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<types>

<xsd:schema>

<xsd:import

namespace="http://AppName.internalName.com/ns/edb/services/eDBInBoundCSDServices/2003-08"

schemaLocation="eDBInBoundCSDServices.xsd" />

<xsd:import

namespace="http://xmlns.internalName.com/SIPD/eDBInBoundCSD/2013/02/ServiceRequests"

schemaLocation="eDBInBoundCSDServiceRequests.xsd" />

<xsd:import namespace="http://AppName.internalName.com/ns/fbc/messages/2003-08"

schemaLocation="AppNameHeader.xsd" />

</xsd:schema>

</types>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

<part name="body"

element="edbs:INBOUND_BULK_UPDATE_SERVICE_REQUEST_HEADER_DATAResponse" />

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</message>

</operation>

</operation>

</operation>

</operation>

</operation>

</operation>

</operation>

</operation>

</operation>

</operation>

</portType>

<soap:binding style="document"

transport="http://schemas.xmlsoap.org/soap/http" />

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

<soap:operation soapAction="" style="document" />

<input>

<soap:header message="tns:ServiceInputHeader" part="ServiceInputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</input>

<soap:header message="tns:ServiceOutputHeader" part="ServiceOutputHeader"

use="literal" />

<soap:body parts="body" use="literal" />

</output>

<soap:fault name="Errors" use="literal" />

</fault>

</operation>

</binding>

<soap:address

location="http://internalName.com:9018/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://.internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://pidbwebqa.internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://pidbweblc.internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

<soap:address

location="http://.internalName.com:8888/eDBInBoundCSD/eDBInBoundCSDServices" />

</port>

</service>

</definitions>

Soup Request

<?xml version="1.0" encoding="UTF-8" ?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Header>

<ServiceName>INBOUND_GET_SERVICE_REQUESTS</ServiceName>

</ServiceInputHeader>

</soap:Header>

<soap:Body>

<INBOUND_GET_SERVICE_REQUESTS xmlns="http://AppName.internalName.com/ns/edb/services/eDBInBoundCSDServices/200308">

<ROW_LIMIT>10</ROW_LIMIT>

<RETURNING_DOCUMENTS_IND>Y</RETURNING_DOCUMENTS_IND>

<SERVICE_REQUEST_ID>1921169</SERVICE_REQUEST_ID>

<ENCRYPTED_SERVICE_REQUEST_ID />

<CREATION_TMSTP_BEGIN />

<CREATION_TMSTP_END />

<SYSTEM_STATUS_CD />

<RD_DOCTYPE_NM />

<RD_DOCTYPE_VERSION_NUM />

<SRT_REQUEST_TYPE_CD />

<ORG_ORGANIZATION_CD />

<CUSTOMER_ID>123</CUSTOMER_ID>

<SR_SERVICE_REQUEST_ID />

<USER_STATUS_CD />

<EXTERNAL_SYSTEM_KEY />

<PROCESS_STATUS_CD />

<ACCOUNT_NUM />

<EMAIL_ADDRESS_TXT />

<REP_ID />

<REQUESTOR_ID />

<REQUESTOR_ID_TYPE_CD />

<SECONDARY_CUSTOMER_ID />

<UPDATING_ORGANIZATION_CD />

<UPDATE_TMSTP_BEGIN />

<UPDATE_TMSTP_END />

<CHANNEL_CD />

<DOCUMENT_TYPES>

<DOCUMENT_NAME_TXT>APPDOC</DOCUMENT_NAME_TXT>

</DOCUMENT_TYPES>

</INBOUND_GET_SERVICE_REQUESTS>

</soap:Body>

</soap:Envelope>

Thomas Bayer

unread,

Feb 20, 2015, 5:30:42 PM2/20/15

to membrane...@googlegroups.com

Hi Gary,

Am 19.02.15 um 18:09 schrieb Gary W:

Hi Thomas, Thank you for the fast reply.

More info below.

For soap-proxy port 2017

<html>

<head>

<title>Bad Gateway</title>

</head>

<body>

<h1>Bad Gateway</h1>

<p>Target http://internalName:9018/eDBInBoundCSD/eDBInBoundCSDServices is not reachable.</p>

</body>

</html>

The host internalName on port 9018 is not reachable. If you are using a soapProxy make sure the endpoint address is right. You can make a lokal WSDL copy correct it there and reference it.

For soap-proxy 2018

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Body>

<soapenv:Fault>

<faultcode>soapenv:Server</faultcode>

<faultstring>Message validation failed!</faultstring>

<detail>Validation failed: org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 110; cvc-elt.1: Cannot find the declaration of element 'INBOUND_GET_SERVICE_REQUESTS'.;</detail>

</soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

Here the request message is not valid against the schema referenced from the WSDL. If you do not want validation you can turn it off. Just delete the <validator> tag:

</soapProxy>

Please let me know if this does not help you.

Cheers,
Thomas

Gary W

unread,

Feb 23, 2015, 3:35:05 PM2/23/15

to membrane...@googlegroups.com

Hi Thomas,

We are moving the ball but i'm not sure if the new config is right because i get a different error.

<html>

<head>

<title>Bad Request</title>

</head>

<body>

<h1>Bad Request</h1>

<p>

This request was not accepted by

<a href="http://www.membrane-soa.org/esb-doc/">Membrane Service Proxy</a>

. Please correct the request and try again.

</p>

</body>

</html>

this is what is in the config.

<soapProxy port="2018" wsdl="http://localhost/eDBInBoundCSDServices.wsdl"

host="internalServer:8888">

</soapProxy>

since i moved the wsdl to local server, i add the host tag. Is this right?

Thomas Bayer

unread,

Feb 23, 2015, 5:08:02 PM2/23/15

to membrane...@googlegroups.com

Hi Gary,
the error means that no proxy matched the incomming request. You used the host-attribute which means that only requests with a HTTP host header containing this value will match. I do not know if you intend this.

May be you can sketch what you want to do.

Cheers,
Thomas

Am 23.02.15 um 21:35 schrieb Gary W:

--
You received this message because you are subscribed to the Google Groups "membrane-monitor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to membrane-monit...@googlegroups.com.
To post to this group, send email to membrane...@googlegroups.com.
Visit this group at http://groups.google.com/group/membrane-monitor.
For more options, visit https://groups.google.com/d/optout.

Gary W

unread,

Feb 24, 2015, 10:50:35 AM2/24/15

to membrane...@googlegroups.com

Hi Thomas, I really appreciate your help.!

I used the host config statement because originally the servers wsdl had an error and i can't change it on the server.

You suggested for me to create a local copy of it, so i did.

Simple question:

if the wsdl is on localhost. How do I tell the Membrane where the Target Web service is?

I attached a diagram of what i'm trying to do. At first I'm just trying to do a soap proxy from a soap client to another soap server by using a wsdl and schema on the membrane proxy server.

In the near future i will need to convert some soap requests to restful.

The reason for this. I don't have access to the client and i don't have access to any of the servers. Hence perfect middleware solution for the Membrane.

I'm happy to develop to the Membrane, and contribute to the open source but I've had problems with artifacts and doing a build. If you would like to use me to test builds, please let me know.

Best Regards

Gary

simpleProxy.pdf

Thomas Bayer

unread,

Feb 24, 2015, 3:19:53 PM2/24/15

to membrane...@googlegroups.com

Hi Gary,

Am 24.02.15 um 16:50 schrieb Gary W:

Hi Thomas, I really appreciate your help.!

I used the host config statement because originally the servers wsdl had an error and i can't change it on the server.

You suggested for me to create a local copy of it, so i did.

Simple question:

if the wsdl is on localhost. How do I tell the Membrane where the Target Web service is?

Edit the location attribute of the address element inside the WSDL. Like here:

<wsdl:port name="BLZServiceSOAP11port_http" binding="tns:BLZServiceSOAP11Binding">

<soap:address location="http://targetServer:targetPort/axis2/services/BLZService"/>

</wsdl:port>

I attached a diagram of what i'm trying to do. At first I'm just trying to do a soap proxy from a soap client to another soap server by using a wsdl and schema on the membrane proxy server.

In the near future i will need to convert some soap requests to restful.

Those diagrams help me a lot. You can also write into the diagram portnumbers and paths.

The reason for this. I don't have access to the client and i don't have access to any of the servers. Hence perfect middleware solution for the Membrane.

Membrane should be perfect for this job.

I'm happy to develop to the Membrane, and contribute to the open source but I've had problems with artifacts and doing a build. If you would like to use me to test builds, please let me know.

Building should now be easy. To build 4.0.19 just make sure you are using Java 1.7 and then:

git clone --branch v4.0.19 https://github.com/membrane/service-proxy
cd service-proxy/
mvn install

Please let me know if there are some issues left.

Cheers,
Thomas

Gary W

unread,

Feb 25, 2015, 9:50:06 AM2/25/15

to membrane...@googlegroups.com

Thank you Thank you Thank you!

I'm able to use soap-proxy out of the box. Thanks for the build tips. I will give that a try.