Hello Johannes,
to make it a little bit clearer:
Element *publishWSDL* is used to configure synapse to have a wsdl for
the proxy service (must not be the same to the wsdl of the service which
should be invoked-> think of transformation, for example!).
The Element *endpoint *and its child *wsdl* are used to get the endpoint
of the specified wsdl service to send the request to that endpoint
reference.
Hope, it is clearer now.
Thanks,
Jens
Jens Goldhammer schrieb:
Hello Johannes,
did you put the wsdl in the registry (filesystem root-folder of esb->
folder registry-> create folder wsdl->put the wsdl-file in it!)?
Synapse does not use the wsdl which is defined by the endpoint-element!
Look at
http://wso2.org/project/esb/java/1.6/docs/administratorguide.html#Adding
for using the admin console to publish the wsdl (step 11)!
I think, you have to click on Advanced while creating the proxy.
Bye,
Jens
Johannes Elsinghorst schrieb:
Hello,
i added the "publish wsdl key" manually to the config-> same error.
Where can i do this via the admin console? There is no such option
when i setup the endpoint.
thanks, Johannes
Hello Johannes,
you can use the publishWSDL-element to configure Synapse that it has
to publish the wsdl for your proxy service. You can also made this
via the admin console of WSO2 ESB.
Example of a synapse.xml:
<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse";>
<syn:registry provider="org.wso2.esb.registry.ESBRegistry">
<syn:parameter name="root">file:registry/</syn:parameter>
</syn:registry>
<syn:proxy name="ags" transports="http" startOnLoad="true">
<syn:target>
<!-- -->
<syn:target>
<syn:publishWSDL key="wsdl/ags.wsdl"/>
</syn:proxy>
</syn:definitions>
The key has to point to a document of the registry (full path-
ags.wsdl is located in the wsdl-folder) specified above.
After that you can get the wsdl by using the url
http://localhost:8080/soap/ags?wsdl
You can find more information on
http://synapse.apache.org/Synapse_Configuration_Language.html.
Hope, that helps.
Bye,
Jens
Johannes Elsinghorst schrieb:
Hi,
i us ethe latest version (wso2-esb-java-1.6) and jdk 1.6.0_05.
this is the configuration:
<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse";>
<syn:registry provider="org.wso2.esb.registry.ESBRegistry">
<syn:parameter name="root">file:registry/</syn:parameter>
</syn:registry>
<syn:proxy name="ags" transports="http" startOnLoad="true">
<syn:target>
<syn:endpoint>
<syn:wsdl service="Catalog"
port="ServiceCatalogPort"
uri="http://windows2003/arcgis/services?wsdl"; format="soap11"/>
</syn:endpoint>
<syn:outSequence>
<syn:send/>
</syn:outSequence>
</syn:target>
</syn:proxy>
<syn:sequence name="fault">
<syn:log/>
</syn:sequence>
<syn:sequence name="main">
<syn:in>
<syn:log level="full"/>
<syn:filter source="get-property('To')"
regex="http://localhost:9000.*";>
<syn:send/>
</syn:filter>
</syn:in>
<syn:out>
<syn:send/>
</syn:out>
</syn:sequence>
</syn:definitions>
thanks, Johannes
Hi Johannes,
Few questions to reproduce this issue; Could you please tell me
the following details please?
1. version of ESB that you are using the
2. jdk version you are using
3. if possible the configuration that you have used to generate the
proxy (you could get this config by traversing to the
Configuration tab of the console, just paste the content on the
text area of the Configuration tab)
If you do not provide a WSDL using the publishWSDL element in the
proxy you can not view the WSDL of that proxy because there is no
WSDL. If this is not the case, can you please provide the above
details so that I can investigate the issue...
Thanks,
Ruwan
Johannes Elsinghorst wrote:
Hi,
i tried to configure a simple prox for a soap ws. when i try to
retrieve the wsdl from the proxy via
http://localhost:8080/soap/myService?wsdl:
i get this error:
08-04-13 13:59:57,812 [192.168.0.137-johannes]
[HttpServerWorker-11] ERROR ServerHandler Unexpected HTTP
protocol error : Transfer-encoding header already present
g.apache.http.ProtocolException: Transfer-encoding header already
present
at
org.apache.http.protocol.ResponseContent.process(ResponseContent.java:67)
at
org.apache.http.protocol.BasicHttpProcessor.process(BasicHttpProcessor.java:304)
at
org.apache.synapse.transport.nhttp.ServerHandler.commitResponse(ServerHandler.java:233)
at
org.apache.synapse.transport.nhttp.HttpCoreNIOSender.sendAsyncResponse(HttpCoreNIOSender.java:360)
at
org.apache.synapse.transport.nhttp.HttpCoreNIOSender.invoke(HttpCoreNIOSender.java:225)
at
org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:478)
at
org.apache.synapse.transport.nhttp.ServerWorker.handleException(ServerWorker.java:476)
at
org.apache.synapse.transport.nhttp.ServerWorker.processGet(ServerWorker.java:320)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:188)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I this a know issue? How can i fix it?
thanks, Johannes
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
