cxf

问题 I have a problem with my cxf dependencies. There is a really huge project that ı working and there are lots of dependencies. My problem is with xerces dependency. There is no older versions of xerces in my pom files, but i am getting the following exception. Do you have any idea about the problem ? Caused by: java.lang.AbstractMethodError: org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; at org.apache.cxf

问题 MTOM is usually used to transfer image data over SOAP (attachments). The image is mapped to a java.awt.Image (at least with CXF). Does the Image object consume a lot more memory than the actual image transferred? Let's say a transferred JPEG is 10MB, how much more space will the Image object consume? UPDATE - I'm not so sure it has anything to do with java.awt.Image at all. Focusing on CXF/MTOM more at the moment: http://cxf.547215.n5.nabble.com/MTOM-large-attachments-eating-up-JVM-heap

问题 I've recently updated my Spring version from 3.2.4.RELEASE to 4.0.7.RELEASE and since then I'm getting this error while loading context. Please let me know if I'll have to make any changes to context xml after updating spring version. Here is the avengers-flow-context.xml : <?xml version="1.0" encoding="UTF-8"?> <beans:beans xmlns:int="http://www.springframework.org/schema/integration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:beans="http://www.springframework.org/schema

问题 I'm using Tomcat 6 and CXF 3 to implement some web services. I need to generate client code by using wsdl2java command on my local server. And it works on http protocol: wsdl2java -frontend jaxws21 -p com.activenetwork.iam.ws.client -d "D:\devtools\workspace\TestClient\src" -encoding utf-8 -client -V http://localhost:8080/IAM/services/employee?wsdl But, after i updated the server to https protocal, the command doesn't work anymore wsdl2java -frontend jaxws21 -p com.activenetwork.iam.ws.client

问题 I trying to build an UI to view the SOAP transactions that were sent out from my application. A typical scenario is that each user transaction include multiple web-service request to multiple systems and I am generating a transactionId for that user transaction and Logging all the logs with that transactionId in log file, so that the log file can be searched using the transactionId and the corrosponding log statements can be displayed on UI. So, I am able to append the generated transactionId

问题 As title, we had a simple service design that uses a cxf:proxy endpoint inside an http-inbound enpoint, and the Mule server is behind load-balancer which does ssl offloading. When user requested with https ://url?wsdl, in the returned wsdl, we found mule writes the service address in http . Is there any way that we could change it to https here? We are using mule 3.5.2 here. PS. The Load-balancer is F5 and belongs to 'network team', we could ask for the X-Forwarded-Proto header, but only if

问题 I am using JAXRSClientFactory to instantiate REST clients for integration test purpose. Between two tests, I restart my Jetty server, and instantiate new REST clients, to the same URL. However, it seems that CXF is using some kind of connection pooling, or connection keep-alive system under the hood, since I get connection errors for the first test following the restart of the server. I have not found anything stating the use of connection pooling in the documentation though : It is the case

问题 For various reasons I need to try out the jaxws21 frontent in my build. So I followed the tip on this answer, adding to the wsdl options: <extraargs> <extraarg>-fe</extraarg> <extraarg>jaxws21</extraarg> </extraargs> But my build complains: Could not find jaxws21 frontend within classpath How do I resolve this? BTW, my pom.xml includes: <dependency> <groupId>javax.xml.ws</groupId> <artifactId>jaxws-api</artifactId> <version>2.2.8</version> </dependency> Could this be the culprit? If so, which

问题 I have a CXF web service which processes requests containing base64 strings. Some of the requests take long time which exceeds our requirements. I want the processing to complete by 3 seconds but most requests are taking 12 seconds. When i trace the processing of the interceptors, the DocLiteralInInterceptor is consuming the most time. As per documentation, this interceptor checks the SOAPAction and binds the message. I am using aegis binding and tried to disable the validation with schema

问题 I want to transform an existing XML-based webservice to a REST webservice. While the services are working already, I'm struggling with implementing the security. In the former implementation, we used interceptors like this (file ws-server-context.xml ): <jaxws:endpoint id="someService" implementor="..." address="/..." > <jaxws:inInterceptors> <bean class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" /> <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"> <constructor-arg>