[ 
http://issues.apache.org/jira/browse/AXIS2-350?page=comments#action_12361480 ] 

Davanum Srinivas commented on AXIS2-350:
----------------------------------------

If you notice closely, the service name that i have in my original wsdl is 
butchered. Axis2 insists on using /wsdl:defininitions/wsdl:portType/@name as 
the name of the service instead of /wsdl:defininitions/wsdl:service/@name. 

<end_user hat="on">
i am an enterprise developer following WSDL-First, then i *REALLY* need the 
service to look/act in a certain way. I definitely don't want Axis2 to dictate 
what my service names look like. I'd appreciate if the wsdl2java code 
generation generates code which i can then deploy to get the results that i 
expect. Please note that i *do* want to generate both my service and client in 
one shot in my 8 hour build process. If Axis2 mucks around with my wsdl, then i 
can't do that. I *REALLY* don't want to deploy to a server to figure out what 
the AXIS2 generated wsdl looks like and i certainly don't want to store 2 
wsdl's in my SVN one for the server and one for the client. 
</end_user>

> Service.WSDL is not picked up
> -----------------------------
>
>          Key: AXIS2-350
>          URL: http://issues.apache.org/jira/browse/AXIS2-350
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Davanum Srinivas

>
> Hi,
> I ran "java org.apache.axis2.wsdl.WSDL2Java -d adb -o work -s -p samples.ping 
> -t -ss -sd -uri axis2\modules\security\interop\ping.wsdl" then created an 
> aar, dropped the services.xml and service.wsdl as follows. 
> PingPort
> \---META-INF
>         service.wsdl
>         services.xml
> When i run tomcat and view the wsdl. it's not the correct one that i placed 
> in the META-INF directory.
> thanks,
> dims

-- 
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

Reply via email to