The Axis2 WebService namespace defaults to the reverse of the package name, and the default name can be modified by the following two entries: the Service target Namespace services target namespace only works in the WSDL generation process. At run time, if someone tries to view the WSDL using the? WSDL, the target namespace in the generated WSDL file is the value specified in the Services.xml file. At the same time, in order to use the custom WSDL file, we put the WSDL file into the Meta-inf directory, in this case to overwrite the original target namespace, but also by adding the target namespace to the Services.xml file to achieve. The default value for the target namespace is http://ws.apache.org/axis2. To specify the target namespace, we need to add an optional targetnamespace attribute to the service node, as in the following example: ... Schema target namespace when generating a WSDL file (runtime) or schema (at deployment), if the WSDL file is not found in the Meta-inf directory, You can specify a custom schema target namespace by adding a schema node to the Services.xml file. When deploying, if you do not specify a schema target namespace, the target namespace is generated based on the full pathname of the service implementation class. For example, if the full path name of the service class is Org.apache.axis2.FooService, the generated schema namespace is http://FooService.axis2.apache.org/xsd if you want to use a custom value, Just add the following nodes to the Services.xml file. specific can be said AIXS2 service.xml configuration detailed article: http://paggywong.iteye.com/blog/1350448 began to want to WebService annotation method to solve, Theoretically AXIS2 is supported, but for some reason the service cannot be accessed after using annotations, it is only solved with the above method.
2015 14th Monday
