This project collects a few AXL/Java samples showing use of WSDL-based code generation and attempts to implement some important best-practices: https://github.com/CiscoDevNet/axl-java-samples
The methods you are listing above would come from a library autogenerated by JAX-WS (this project uses this implementation: https://github.com/eclipse-ee4j/metro-jax-ws) by reading the AXL WSDL files.
AddSipTrunkReq() represents an individual SOAP method, here corresponding to addSipTrunk. The JAX-WS code generation should create such methods for all of the AXL requests.
- XSipTrunk() represents an XSipTrunk element in the AXL schema. AXL objects are made up of elements and sometimes sub-elements, e.g. https://pubhub.devnetcloud.com/media/axl-schema-reference/docs/Files/AXLSoap_XSipTrunk.html#Link11D2 . In order to build up a 'complete' AXL objects for use with a request, you may need to instantiate a bunch of sub-elements, set their properties, and assign them to the root object.
- XFkType() this represents a 'foreign key' type. In general it will be an element consisting of a name or unique UUID referencing another AXL object (corresponding to a record in another UCM database table linked by a foreign key)
- AXLAPIService() creates the JAX-WS object representing the AXL SOAP service
- getAXLPort() returns the specific SOAP port of the AXL service
Use of AXL with JAX-WS is pretty complicated/involved, and as with any specific framework based on WSDL consumption (see .NET or Zeep) is not directly supported by Cisco. If you only have a few simple AXL requests you need to deal with, it may be (far) easier to just treat the requests as XML strings sent over HTTP, rather than trying to use the WSDL-based stack...
