Hello,
Thanks for your reply, I will change my wsdl to multiple wsdls, so
that it works with axis2.
But I don't really understand your decision to only support one port
type for each wsdl. The wsdl specification gives this service
granularity decision explicitly to the service designer but you make
this decision fix by the architecture of Axis2. Of course, it is not a
really big issue and you can work around by defining a service for
each port type, but I think for standard conformity you have to
support multiple port types and bindings for a service. Is there an
architectural reason for this design decision? It would be good to
know, since I have to propagate this granularity decision.
Best regards,
Kai Huener
On 10/19/06, Deepal Jayasinghe (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/AXIS2-1443?page=all ]
Deepal Jayasinghe resolved AXIS2-1443.
--------------------------------------
Resolution: Fixed
At the code generation time we pick only one port to generate the code and only
the corresponding binding and porttype are used. So even if you have multiple
of them only one of them will be actually using that is why after you codegen
you get wsdl with only one port and one portType.
P:S - There is no bug in your code or Axis2 .
> multiple port types not supported?
> ----------------------------------
>
> Key: AXIS2-1443
> URL: http://issues.apache.org/jira/browse/AXIS2-1443
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: nightly
> Environment: Windows XP, Apache 2.2, Tomcat 5.5, Axis 2 nighly, 1.1
branch, self-compiled xmlSchema.jar from current svn
> Reporter: Kai Huener
> Attachments: WSAgreementService.aar, WSAgreementService.wsdl
>
>
> Hello,
> When I create an aar by using the auto-generated ant build.xml, all class
files are included, but the service.xml as well as the included wsdl are much to
short, they only include one port type. By the way, no Error message is thrown.
Why does Axis2 behave like this? Are multiple port types not supported, or is
there any fault on my side? The original WSDL as well as the resulting aar will be
attached.
> Thanks in advance,
> Kai Huener
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.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]
