axis2

Axis2 generated Stubs are thread-safe?

瘦欲@ 提交于 2019-12-01 08:17:31
Are the Stubs generated by WSDL2JAVA (using XMLBeans binding option) through Axis2 1.5.4 thread-safe? Actually I have created one Stub for a Web Service that I am invoking through multiple threads. I have configured my own MultiThreadedHttpConnectionmanager and set the HTTPConstants.REUSE_HTTP_CLIENT as well but I am seeing some NullPointerExceptions in stub._getServiceClient().cleanupTransport that I call after each invocation. Sometimes the threads hang too. At the same time I noticed that in the generated Stub in the Web Service operation method, cleanup() is called already in the finally

MyEclipse 8.5 安装 axis2 插件

吃可爱长大的小学妹 提交于 2019-12-01 07:49:19
摘要 一:MyEclipse安装axis2插件简述 二:浅析安装失败的原因 本文安装环境: MyEclipse 8.5 axis2-eclipse-service-plugin-1.62.zip axis2-eclipse-codegen-plugin-1.62.zip 正文: 一:MyEclipse 安装axis2插件简述 MyEclipse安装axis插件的方法比较简单,axis2官网出的说明也十分简明,下载zip包,解压放置到MyEclipse_HOME/dropins目录即可。具体说来如下: 1:下载axis2的两个eclipse-plugin.zip (axis2-eclipse-service-plugin-1.62.zip, axis2-eclipse-codegen-plugin-1.62.zip) 2:将解压出的两个jar包拷贝到MyEclipse_HOME/dropins(org.apache.axis2.eclipse.codegen.plugin_1.6.2.jar, org.apache.axis2.eclipse.service.plugin_1.6.2.jar) 3:重启MyEclipse即可。 可是当我无限憧憬着重启MyEclipse之后得到确实如下的报错信息(如图:failure. figure),当然File--new

Java client for SOAP web service with NTLM authentication

折月煮酒 提交于 2019-12-01 05:45:09
I spent many days and nights trying to find a proper Java framework that could connect to Microsoft Dynamics CRM which uses Negotiate/NTLM authentication. I tried all existing suggestions on Stackoverflow and other resources with JAX-WS, Axis2, CXF with various HTTP protocol handlers. No one of them worked as expected. The best approach currently is Axis2/commons-httpclient-3.1, where I can trace at least all three phases with NTLM digest, however the target IIS still refuses the authentication with 401 Unauthorized. Apache CXF — both with a built-in Java6 NTLM support and jCIFS, which some

Does WCF FaultException<T> support interop with a Java web service Fault

早过忘川 提交于 2019-12-01 00:48:08
I have written a java axis2 1.4.1 web service and .net 3.5 WCF client and I am trying to catch the wsdl faults thrown. Unlike .net 2.0 the .net 3.5 claims to support wsdl:fault and the service reference wizard does generate all the correct fault classes in the client proxy. But when I try to catch a fault it doesn't seem to correctly serialise so that I can only catch (FaultException ex) and not the type I actually threw using FaultException<T> I had a look inside my reference.cs I can see wizard has added correct FaultContract to the my opeation. [System.CodeDom.Compiler

Getting raw XML SOAP-response on client side using ADB-stubs created by AXIS2

断了今生、忘了曾经 提交于 2019-11-30 18:59:59
I access a SOAP service using ADB-stubs created by AXIS2. I would like to log the raw XML response of any Axis Fault, that is returned by the service. I can catch those errors as "ServiceError". However, I do not find a way to retreive the raw XML (see example below). I found a way to access the raw XML request / response for regular processing, using getOMElement (see example below). However, this does not work for faults. How do I get the raw XML fault using ADB stubs? Example Java code: public void testRequest(String URL) throws AxisFault { MyServiceStub myservice = new MyServiceStub(URL);

How to preserve the Content-Type header of a Tomcat HTTP response sent through an AJP connector to Apache using mod_proxy

穿精又带淫゛_ 提交于 2019-11-30 14:21:50
I'm having a problem with an incorrect HTTP Response Content-Type header while accessing an Axis2 web service hosted in Tomcat behind Apache through an AJP/1.3 connector. I can access the web service without problems in the browser through its RESTful interface and I can see the results but somehow Apache is changing the response Content-Type header sent by Tomcat from text/xml to text/plain and it prevents me from consuming the web service through SOAP in NetBeans, because of an Unsupported Content-Type: text/plain Supported ones are: [text/xml] exception. Here's the relevant section of my

Axis error about runtime location

北城以北 提交于 2019-11-30 13:17:33
The error is: Exception occurred while reading or writing file {0}The Axis2 facets cannot be installed since the Axis2 runtime location has not been set. Go to the Web Services preference page and set the Axis2 runtime location under Axis2 Preferences. In the preferences mentioned, the location is set correctly and in fact, it says "Axis2 runtime loaded successfully" after loadign the correct runtime location. So what's going on? Any solutions other than re-installing eclipse or creating a new workspace? I am using Axis2 1.4.1 and eclipse. Re-check your axis version used with Eclipse (to be

How does a wsimport generated client work?

雨燕双飞 提交于 2019-11-30 10:46:51
问题 Before anything else, I want you to know that I can already connect to the web service server. I'm asking this question because I want to gain a deeper knowledge on how a wsimport generated client works. Based from my research, wsimport uses JAXWS. Please note that I have no knowledge from JAXWS. I generated my client using wsimport. The WSDL I used is from an Axis2 web service and was automatically generated by Axis2. The classes below are the results of wsimport: Under com.datamodel.xsd

Axis2 Web Service Client Generation - Types without modifying the client

久未见 提交于 2019-11-30 10:22:48
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 already existing java files. If you really want to reuse existing classes, you can call the Axis2 API

change soap:address location from http to https

风流意气都作罢 提交于 2019-11-30 09:57:01
问题 yes my application server runs on https. Client is asking to change the soap address from http to https. client is asking that whenever he want 2 see the wsdl through broswer the soap address should come as https i already added this in axis2.xml... <transportReceiver name="https" class="org.apache.axis2.transport.http.SimpleHTTPServer"> <parameter name="port">8443</parameter> </transportReceiver> I added the below in service.xml <transports> <transport>HTTPS</transport> </transports> after