Diep Luong created AXIS2-5927:
---------------------------------
Summary: Incorrect stub generated when upgrading from axis2 v1.5.1
to v1.7.4
Key: AXIS2-5927
URL: https://issues.apache.org/jira/browse/AXIS2-5927
Project: Axis2
Issue Type: Bug
Components: codegen
Affects Versions: 1.7.4
Reporter: Diep Luong
I'm having a problem with generating the correct stub after upgrading from
axis2-1.5.1 to axis2-1.7.4. The WSDL I'm working with has a service with 2
ports defined having different binding. When generating the client code, I'm
only getting the stub for the second port. With axis2-1.5.1, I was getting the
stub for the first port. I'm using another tool that is part of a larger
product. The tool I'm using uses CodeGenerationEngine to generate the client
code and is not using the command line option -pn. I know that using the
command line option -pn will create the stub that is needed. The default
behavior (when -pn is not specified) seems different between these axis2
version. I've tried switching the order of the port definition in the WSDL but
it didn't make a difference. With axis2 1.7.4, how is the port selected if -pn
option is not specified? Is it possible to apply the default behavior of 1.5.1
to 1.7.4?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
