axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nirmit Desai (JIRA)" <>
Subject [jira] Commented: (AXIS2-1068) Axis2 deployment does not preserve the original WSDL from META-INF
Date Thu, 24 Aug 2006 20:18:03 GMT
    [ ] 
Nirmit Desai commented on AXIS2-1068:

The WSDL returned by ?wsdl is preserved when I set the useOriginalwsdl to true. But I feel
that this is still a bug as Axis should never change the name of the portType. The very reason
behind separation of port from portType was that there could be many ports supporting a portType
in separate WSDLs (ofcourse referring to the original namespace). What good does it do to
rename the portType anyway?

> Axis2 deployment does not preserve the original WSDL from META-INF
> ------------------------------------------------------------------
>                 Key: AXIS2-1068
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment, wsdl
>    Affects Versions: 1.0
>         Environment: Windows XP, Tomcat 5.5
>            Reporter: Nirmit Desai
>            Priority: Critical
>         Attachments: TSE1MemberService.aar
> I need many services to implement a portType. So the name of the service ius different
from the name of the portType. 
> I make sure that the name of my service in the WSDL, in the services.xml, and the name
of the deployed aar are the same. I put my WSDL in META-INF, set useOriginalwsdl in services.xml
to true.
> When I deploy this aar, and I traverse to the WSDL from the Axis2 services page, I see
that Axis to renames the portType to suit <serviname>PortType. Thus, my original portType
name is lost. 
> This is a show-stopper for me as I have other services accessing the WSDL given EPRs
and verifying the portType imploemented by that EPR. I have no way of getting around this.
> Th attached aar demonstrates this. It should be easily deployable. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message