Axis2 1.6 4 Download
Jayme Bostic
I'm trying to select the axis2 Web Service facet (step 6) but I'm getting this error message in eclipse:"Axis2 Web Services Core 1.1 requires Dynamic Web Module with version matching expression "2.2,2.3,2.4,2.5"
Update: I had downloaded and installed axis2 1.5.4 and then in eclipse I went into "windows->preferences->web services->axis2 preferences". Under the "axis2 runtime" tab I specified the axis2 location. The message "Axis2 runtime loaded successfully" appeared.
Since my end goal was to make a webservice, I went to look for axis2. I couldn't find any Ubuntu packages for axis2, so I next went and downloaded axis2 v 1.6.1 from here and unzipped it in my home directory. To get started, I pointed a symbolic link from /var/lib/tomcat6/webapps/axis2 -> /home/doug/.../axis2-1.6.1/webapp/ based on these instructions.
The quick start guide you are referring to doesn't say that you should create a "symbolic link from /var/lib/tomcat6/webapps/axis2 -> /home/doug/.../axis2-1.6.1/webapp/". It says the you should "Copy the axis2.war file to the webapps directory of your servlet engine". There are two ways to get the axis2.war file:
My main confusion, though, is around what exactly it takes to 'engage' the Addressing module. Should it be enough to set up my ConfigurationContext with an axis2.xml file that has a reference to the addressing module? Like this? :
[INFO] Unable to sendViaPost to url[ ] org.apache.axis2.AxisFault: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
For each protocol (HTTP and/or HTTPS), an AxisServletListener instance must be declared in axis2.xml. If only a single protocol is used, no further configuration is required. For example, if only HTTP is used, the following declaration must be present in axis2.xml:
If both HTTP and HTTPS are used, then things become a bit more complicated. The reason is that in order to expose WSDLs with correct endpoint URIs, AxisServlet must know the ports used by HTTP and HTTPS. Unfortunately the servlet API doesn't allow a Web application to discover all configured protocols. It only provides information about the protocol, host name and port for the current request. If only a single AxisServletListener is configured, then this information is enough to let AxisServlet auto-detect the port number. If both HTTP and HTTPS are used (or if WSDLs are retrieved through transports other than AxisServlet), then AxisServlet has no way of knowing the port numbers until it has processed at least one request for each protocol. To make WSDL generation predictable in this scenario, it is necessary to explicitly configure the port numbers in axis2.xml, such as in the following example:
You get this because the certificate you used to secure the axis2 service is not trusted. You need to import that public certificate or the CA cert that signed it to a key store and set the following two system properties - in your client code
Another thing that I feel I should mention is that, this web service will work if I change the axis version in CF Admin>Web Services to version 1. But This isn't an option because when I do this on production more web services break. This leads me to believe that its some other configuration within the axis2.xml.
I have embedded an axis2 webservice into a web application of mine. It works great as long as I don't need to specify the location of axis2.xml (i.e. if everything is left default for axis2 initialization).
However, I now need to modify the transporter to use my SOAP webservice over https. For this, I have 1) copied the axis2.xml file of a standalone axis2 distribution and stripped a lot of things from it and 2) modified my web.xml file like this after a lot of trials & error:
Apparently, not specifying the path and putting the file inside WEB-INF/conf/axis2.xml is enough to make it work. It might not have worked in the first place because my axis2.xml was not complete/valid.
Error message:-
log4j:WARN No appenders could be found for logger (org.apache.axis2.description.AxisOperation).log4j:WARN Please initialize the log4j system properly.org.apache.axis2.AxisFault: Exception occurred while trying to invoke service method TestInsert at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) at org.apache.ws.axis2.STStub.testInsert(STStub.java:1443) at org.apache.ws.axis2.WSTSample2.main(WSTSample2.java:33)
According to this page, all I really need to do to enable my service for connections via SSL is to update the axis2.xml file and include a new "transportReceiver" node for HTTPS. I did that and regenerated my client code to use the secure endpoint. It doesn't work.
[INFO] Listening on port 8443 [ERROR] Terminating connection listener org.apache.axis2.transport.http.server.DefaultConnectionListener@16d60567 after 10retries in 0 seconds. java.net.BindException: Address already in use: JVM_Bind at java.net.DualStackPlainSocketImpl.bind0(Native Method) at java.net.DualStackPlainSocketImpl.socketBind(Unknown Source) at java.net.AbstractPlainSocketImpl.bind(Unknown Source) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket.(Unknown Source) at java.net.ServerSocket.(Unknown Source) at org.apache.axis2.transport.http.server.DefaultConnectionListener.run(DefaultConnectionListener.java:80) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
I have tried changing the port number in axis2.xml (for example, to 8445), and that sort of works. The server is able to start cleanly, but eventually, the same errors start showing up. For example, when I retrieve the WSDL, I see the error via the console (though the WSDL does show up). Also, if I try to actually use the service when on port 8445, I get the following error:
But for a specific question... What, exactly, am I doing when I set the transportReceiver nodes in axis2.xml? Am I telling it what ports Tomcat is running on and that it should use, or does Axis2 have its own servers that will start on those ports? It seems to be the latter, but that doesn't make a whole lot of sense to me.
The correct way to configure the servlet transport is described in the Axis2 documentation. The symptoms you are describing suggest that you have a transportReceiver that refers to org.apache.axis2.transport.http.SimpleHTTPServer. Please also make sure that you use a recent version of Axis2 (1.5.6 or 1.6.1).
Having the wsdl you can use the axis2-maven wsdl2code plugin to develop the WSS (web service server-side). This plugin in the version 2.6.0 only generates the source code of your server, but you need to host this code inside an axis2-war distribution or as an aar component.
Having the wsdl you can use again the axis2-maven wsdl2code plugin to generate the WSC (web service client-side). You can specify in the plugin instruction that you want to generate the test code. You can use mvn generate-sources to generate the client stub, move the generated sources and modify the test.
I am newly to JBOSS and AXIS2. As I working on i2b2 platform, on of the steps of i2b2 installation is using axis2 in jboss deployment. The steps are not clear in the guide: 2.4.4 Apache Axis2 - Developers Getting Started With i2b2 - i2b2 Wiki.
Exploits a directory traversal vulnerability in Apache Axis2 version 1.4.1 bysending a specially crafted request to the parameter xsd(BID 40343). By default it will try to retrieve the configuration file of theAxis2 service '/conf/axis2.xml' using the path'/axis2/services/' to return the username and password of theadmin account.
To exploit this vulnerability we need to detect a valid service running on theinstallation so we extract it from /listServices before exploitingthe directory traversal vulnerability. By default it will retrieve theconfiguration file, if you wish to retrieve other files you need to set theargument http-axis2-dir-traversal.file correctly to traverse tothe file's directory. Ex. ../../../../../../../../../etc/issue
See the documentation for the slaxml library. creds.[service], creds.global See the documentation for the creds library. http.host, http.max-body-size, http.max-cache-size, http.max-pipeline, http.pipeline, http.truncated-ok, http.useragent See the documentation for the http library. smbdomain, smbhash, smbnoguest, smbpassword, smbtype, smbusername See the documentation for the smbauth library. Example Usage nmap -p80,8080 --script http-axis2-dir-traversal --script-args 'http-axis2-dir-traversal.file=../../../../../../../etc/issue' nmap -p80 --script http-axis2-dir-traversal Script Output 80/tcp open http syn-ack_http-axis2-dir-traversal.nse: Admin credentials found -> admin:axis2 Requires
- creds
- http
- io
- nmap
- shortport
- stdnse
- string
- table
- Paulino Calderon License: Same as Nmap--See -legal.html
That logging is coming from axis2 and is for generated client code. We already log any exceptions that we get when invoking a client into the product's main logs so I would not expect the axis2.log to be needed for any troubleshooting sessions.
I had this problem due to a version mismatch of axis2-adb. Safest way to deal with this problem is to have a look at the lib folder of the eclipse plugin (eclipse/(dropinsplugins)/ ... .jar). Then look for the versions of the dependecies and include them (the ones you actually need) in your build path.
760c119bf3