[
https://issues.apache.org/jira/browse/AXIS2-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135168#comment-13135168
]
Gaël de Chalendar commented on AXIS2-4654:
------------------------------------------
I'm coming here from https://wso2.org/jira/browse/WSFCPP-140 where I describe
the same problem with the way to reproduce it for WSO2 WSDL2CPP. I think it is
the same issue.
If it is, I really don't understand the "Won't Fix" and "This is by design": It
seems that this makes axis2 not compatible with wsdl, don't it ? My example
wsdl are perfectly valid and in fact they are handled well by gSOAP for example.
Any explanation (or pointer to) for the rationale of this decision ? Thanks in
advance.
> Wsdl2Java generates classes only for one porttype
> -------------------------------------------------
>
> Key: AXIS2-4654
> URL: https://issues.apache.org/jira/browse/AXIS2-4654
> Project: Axis2
> Issue Type: Bug
> Components: wsdl
> Affects Versions: 1.5.1
> Reporter: Peterka
> Priority: Critical
>
> If you call wsdl2java with option -ap (all ports) you still wrongly get only
> classes and definition for one porttype.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
