Is there some conflict between ProcessManager AXIS version with the newly WSDL standard?  
After sending the defined Application to ProcessManager Server, and the ProcessManager Server will generate the Web Services Client code with AXIS.
But there has some conflict between the 'Web Service', 'Port' properties of defined Application and the generated Java Classes Names.
The Java Class name will add '_Port' and '_Service' additionally to the port and service properties names. So when executed the BP, there will be some ClassNotFoundException.

Check the AXIS Web Service Client Code Generator API.
Because if the 'PortType' and 'Service' in the WSDL has the same name, the generated web service client classes name will be forced with the suffix '_Service' and '_PortType'.

Hence it is suggested to keep difference between the 'PortType' name and 'Service' name in the WSDL file. And this work well.