You’ll have to set the CURLOPT_RETURNTRANSFER option to true. $ch = curl_init($url); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, $params); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $result = curl_exec($ch); curl_close($ch); The response to your request will be available in the $result variable.
So, it looks like I’ve found possible answer while combining JAX-WS & JAXB related answers from SO (I would really appreciate if somebody experienced in these technologies can check whether following is correct): The obvious thing for me is to add SOAP message handler and alter header of SOAPMessage instance in it: import javax.xml.ws.Binding; import … Read more
Maybe it’s late for you and I’m not sure if this may work, but you can try. First you need to implement a SoapHandler and, in the handleMessage method you can modify the SOAPMessage. I’m not sure if you can modify directly that prefix but you can try: public class MySoapHandler implements SOAPHandler<SOAPMessageContext> { @Override … Read more
Well, I found the solution. (based on http://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#ACCESS_EXTERNAL_SCHEMA) Create a file named jaxp.properties (if it doesn’t exist) under /path/to/jdk1.8.0/jre/lib and then write this line in it: javax.xml.accessExternalSchema = all That’s all. Enjoy JDK 8.
SOAPAction is required in SOAP 1.1 but can be empty (“”). See the comment here First of all you should try to create new SOAP project using your link to wsdl file. After that try to do request from SOAP UI. Try to run “doCommand” action. Look at the result. Than you can compare it … Read more
For anyone suffering from the same problem; I’ve found a solution for consuming the web service as a Service Reference (WCF). The BasicHttpBinding.MessageEncoding property needs setting to “Mtom”. Here’s a snippet of the required config setting: <configuration> <system.serviceModel> <bindings> <basicHttpBinding> <binding messageEncoding=”Mtom”> </binding> </basicHttpBinding> </bindings> </system.serviceModel> </configuration> Edit: If you are having the same issue … Read more
As hinted in a comment to Jon’s answer, my recommendation would be to use a JAX-WS implementation like JAX-WS RI (which is included in Java 6) or Apache CXF. I’ll use JAX-WS RI to illustrate my answer as it’s available out of the box, on the command line (to explain the steps) but I’d recommend … Read more
Have you tried overriding HttpEntityEnclosingRequestBase as follows: import org.apache.http.client.methods.HttpEntityEnclosingRequestBase; import java.net.URI; import org.apache.http.annotation.NotThreadSafe; @NotThreadSafe class HttpDeleteWithBody extends HttpEntityEnclosingRequestBase { public static final String METHOD_NAME = “DELETE”; public String getMethod() { return METHOD_NAME; } public HttpDeleteWithBody(final String uri) { super(); setURI(URI.create(uri)); } public HttpDeleteWithBody(final URI uri) { super(); setURI(uri); } public HttpDeleteWithBody() { super(); } } … Read more
What is the best approach to do this JAVA? I would personally NOT use Axis 2, even for client side development only. Here is why I stay away from it: I don’t like its architecture and hate its counter productive deployment model. I find it to be low quality project. I don’t like its performances … Read more
Java 7 defaults to TLS 1.0, which can cause this error when that protocol is not accepted. I ran into this problem with a Tomcat application and a server that would not accept TLS 1.0 connections any longer. I added -Dhttps.protocols=TLSv1.1,TLSv1.2 to the Java options and that fixed it. (Tomcat was running Java 7.)