Where is the axis2.xml file

For axis2, the working directory where JRE is started from should be the bin folder of your Apache Tomcat, while for your program, it will depend on where you made the call to the JRE to start the program from. I would advise you to place your configuration file in a place where is easily accessible. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Where do I place axis2. Ask Question. Asked 10 years, 4 months ago. Active 9 years, 4 months ago. Viewed 3k times. Improve this question. Justin Dearing. Justin Dearing Justin Dearing Add a comment. Active Oldest Votes. You are having this problem because JRE is unable to find the configuration file.

Registering Observers is very useful for additional features such as RSS feed generation, which will provide service information to subscribers. The correct way of registering observers should as follows:. The description of services are specified using services. Each service archive file needs to have a services.

A very simple services. Scope is of several types- "application", "soapsession", "transportsession", "request". The default value if you don't enter any value will be "request". ServiceLifeCycle class is useful when you want to do some tasks when the system starts and when it shuts down. This value will be used when generating the WSDL.

If you do not specify this value, the value will be calculated from the package name of the service impl class. Description : Optional If you want to display any description about the service via Axis2 web-admin module, then the description can be specified here. If the transport element is not present, then the service will be exposed in all the transports available in the system. The transport child element specifies the transport prefix the name of the transport specified in axis2.

There is a compulsory parameter in services. This class is loaded by the MessageReceiver. If the user wants to override it, he has to add the "operation" tag and override it. In a non-Java scenario or if you do not have a service class, then all the operations the user wants to expose by the service has to be indicated in the services. It is specified as follows:. The only compulsory attribute here is "name", which represents the operation name that is going to be exposed.

Any operation can contain module references as well as any number of parameters. The most interesting thing is that you can register custom message receivers per operation. Then the registered message receiver will be the message receiver for the corresponding operation.

You can check to make sure that the service has been properly deployed by viewing the list of services at,. The option -d xmlbeans specifies XML Beans data binding. To generate and deploy the service using JiBX data binding , execute the following steps. Else, simply type "ant generate. The option -d jibx specifies JiBX data binding. The -uw switch unwraps the parameters passed to and from the service operations in order to create a more natural programming interface. If you generated the code by using WSDL2Java directly, you need to modify the generated skeleton to implement the service if you used "ant generate.

Also, note the directory structure shown in the Creating a service with AXIOM section, duplicated below for completeness. Here you setup the payload for the update and getPrice methods of the service.

Then you setup the Options class, and create a ServiceClient that you'll use to communicate with the service. First you call the update method, which is a fireAndForget method that returns nothing. Lastly, you call the getPrice method, and retrieve the current price from the service and display it.

This class creates a client stub using the Axis Data Bindings you created. Then it calls the getPrice and update operations on the Web service.

It then sends the request and displays the current price. The update method creates an Update payload, setting the symbol to ABC and the price to Now build and run the client by typing ant run. This class creates a client stub using the XML Beans data bindings you created.

Then it calls the getPrice and the update operations on the Web service. It then sends the request and retrieves a GetPriceResponseDocument and displays the current price.

Now build and run the the project by typing ant run. This class uses the created JiBX client stub to access the getPrice and the update operations on the Web service. The getPrice method sends a request for the stock "ABC" and displays the current price. The update method setsnex the price for stock "ABC" to Now build and run the client by typing "ant run.

Axis2 provides a slick and robust way to get web services up and running in no time. This guide presented five methods of creating a service deployable on Axis2, and four methods of creating a client to communicate with the services.

You now have the flexibility to create Web services using a variety of different technologies. Last Published: Version: 1. Axis2 Quick Start Guide The purpose of this guide is to get you started on creating services and clients using Axis2 as quickly as possible. Introduction Let's start with the service itself.