Hello,
I am communicating with ip-cameras using the apache cxf version 3.0.3 and I
am having a problem with one camera, it only responses to every second
request. I contacted the manufacturer and asked for support and provided a
wireshark trace. They said, that I am using the same tcp connection f
According to http://osdir.com/ml/dev-cxf-apache/2013-11/msg00044.html
http-digest doesn't work since Apache CXF 2.7.4 (I am using ApacheCXF 3.0.3
from 2015-01-13). All other search results on google do it exactly the same
way as the link above and I do. Maybe a bug?
--
View this message in conte
I searched the whole web for a solution, but couldn't find any.
Any ideas?
Thank you in advance.
--
View this message in context:
http://cxf.547215.n5.nabble.com/How-to-use-HTTP-Digest-when-communicating-with-a-WebService-using-JaxWsProxyFactoryBean-tp5754858p5755046.html
Sent from the cxf-user
Hello,
I am trying to communicate with a webservice, my java-code looks like this:
final JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
factory.setBindingId("http://schemas.xmlsoap.org/wsdl/soap12/";);
factory.setUsername("user");
factory.setPassword("pass");
factory.setAddress("htt
Here is the stacktrace ...
org.apache.cxf.service.factory.ServiceConstructionException: Could not
resolve a binding for http://schemas.xmlsoap.org/wsdl/soap12/
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:352)
a
Hi together. :)
We have wsdl files without service and generated code with Apache CXF 2.7.
We have a JaxWsProxyFactoryBean and call
setBindingId("http://schemas.xmlsoap.org/wsdl/soap12/";) on it.
This code worked fine.
Now we downloaded Apache CXF 3.0.3 and generated the code again.
Now we get th
Thanks for your suggestions. Since I don't have a fix endpoint and can't
configure with xml-files I have to do everything in java souce code. Do you
have any code examples for me? I don't know wether I did something wrong or
it just didn't work for me. Thanks.
--
View this message in context:
h
Hi,
that didn't work for me. :(
Is there any chance to get the soap message that caused the exception so
that I can log it to my log-file or parse it for more detailed error-codes
in my application?
By the way, I don't have a fix endpoint.
Kind Regards,
Tobse
--
View this message
