axis2

WSO2 ESB 4.8.1 ERROR White spaces are required between publicId and systemId

烂漫一生 提交于 2019-11-29 17:08:19
We are working with WSO2 ESB 4.8.1 with JAVA 1.7.0_55. Always, when we start the ESB and make the first request we receive this error: TID: [0] [ESB] [2015-04-22 10:51:31,067] ERROR {org.apache.synapse.transport.passthru.util.RelayUtils} - Error while building Passthrough stream {org.apache.synapse.transport.passthru.util.RelayUtils} org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,62] Message: White spaces are required between publicId and systemId. at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296) at org.apache

Creating SSL client with Axis2/Java

不想你离开。 提交于 2019-11-29 16:53:06
I'm trying to connect to the WebService that uses SSL but no success. I use Axis2, I found some usefull article: http://people.apache.org/~dumindu/docs/HowToConfigureSSL.html , but it is for C. In this article they set pathes to SERVER_CERT, KEY_FILE and SSL_PASSPHRASE using axis2.xml or C coding. I tried to change configuration file but this doesn't work for me. If somebody know how to set this parameters from within Java code, let me know. I initialized EasySSLProtocolSocketFactory and Protocol instances for different endpoints and register the protocol with unique key like this: /** * This

Axis2 Web Service Client Generation - Types without modifying the client

落花浮王杯 提交于 2019-11-29 15:42:56
问题 Is it possible with Axis2 and Eclipse to generate a Web Service client and have it use java types that you already have in packages instead of creating it's own types. Reason being of course if I have type A already created and it creates it's own Type A I can't just assign variable of type A to variable of type B. The wsdl is being generated from a Web Service deployed to an application server. If it's not possible to generate it from that would it be possible to generate a client from the

Axis2 always receives null parameters even if SOAP request is sent correctly?

故事扮演 提交于 2019-11-29 15:40:32
问题 UPDATE: I HAVE SOLVED THIS PROBLEM NOW - PLEASE SCROLL TO BOTTOM FOR INFORMATION ABOUT FIX Hi guys, I have a web-service written in Java, hosted on an Axis2 / Tomcat / Apache server. My client software is written in C#. I have had a few irritating problems with the way java2wsdl generates the wsdl file, which did cause me a few headaches early on, but with this problem I am completely stumped. Basically what is happening is that the client sees the web service fine, and sends a perfectly

useOriginalwsdl=true is not working in axis2

只愿长相守 提交于 2019-11-29 14:52:13
I have followed contract first approach. So I first wrote the wsdl file and then generated the server side code. But when I hit the url for my web service in the browser then I see the auto generated wsdl file; not the one I had kept inside META-INF folder. I have also set useOriginalwsdl=true in my services.xml file. When I try to view the wsdl in browser, it fires error Unable to generate WSDL 1.1 for this service in description section and If you wish Axis2 to automatically generate the WSDL 1.1, then please set useOriginalwsdl as false in your services.xml in the reason section of error

How do I add a namespace reference to a SOAP response with Apache Axis2 and WSDL2Java

感情迁移 提交于 2019-11-29 10:05:52
I'm looking at the SOAP output from a web service I'm developing, and I noticed something curious: <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Body> <ns1:CreateEntityTypesResponse xmlns:ns1="http://somedomain.com/wsinterface"> <newKeys> <value>1234</value> </newKeys> <newKeys> <value>2345</value> </newKeys> <newKeys> <value>3456</value> </newKeys> <newKeys xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> <newKeys xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> <errors>Error1</errors> <errors>Error2</errors> </ns1

wso2 esb Unsupported Media Type

余生颓废 提交于 2019-11-29 08:46:39
I would like my company to use the Wso2ESB, but I have only two days left to convince them, and the creation of Proxy does not work! I am desperate for a real help for my problem: every proxy that I create seem to produce HTTPSender Unable to sendViaPost to... (why it is unable to send it?) Transport error: 415 Error: Unsupported Media Type (is it a consequence of the fact that it could not send? or a problem in the configuration?) My fresh installation of WSO2 ESB 4.5 is not working with any web service I have tried: JAXWS and C#. I always have the following message LOG: [2012-05-09 08:42:19

axis2 maven example

我的未来我决定 提交于 2019-11-29 06:15:59
问题 I try to use axis2 (1.5.1) version to generate java codes from wsdl files, but I can't figure out what is the correct pom.xml <build> <plugins> <plugin> <groupId>org.apache.axis2</groupId> <artifactId>axis2-wsdl2code-maven-plugin</artifactId> <version>1.5.1</version> <executions> <execution> <goals> <goal>wsdl2code</goal> </goals> <configuration> <wsdlFile>src/main/resources/wsdl/stockquote.wsdl</wsdlFile> <databindingName>xmlbeans</databindingName> <packageName>a.bc</packageName> <

Attach client certificates with Axis2?

非 Y 不嫁゛ 提交于 2019-11-29 03:08:41
问题 Is it possible to easily attach a client certificate to a Axis2 stub generated using wsdl2java? I need to change the client certificate dynamically on a per-request basis, so simply storing it in the keystore won't work for our case. I've found examples where this is being done for non-SOAP calls, but could not find anything related to using the Axis client stubs. Trying to hack the XML for the SOAP call is an option I guess, albiet a painful one! Groan! 回答1: If you want to change which

What is the difference between ?wsdl and ?singleWsdl parameters

醉酒当歌 提交于 2019-11-29 02:25:16
问题 My messaging provider gives me two different kinds of WSDLs to use. http://my.amazonaws.com:8000/webservice/?wsdl http://my.amazonaws.com:8000/webservice/?singleWsdl The first one is an embedded WSDL. Can NOT use it to generate WSDL2java packages and can NOT use JAX-WS to create a connection. The second one is a single WSDL. It can generate Java packages with CXF 3.0's WSDL2java and can use JAX-WS to create a connection. It works very well. Please let me know what is the difference between