Rajesh,

thanks, your suggestion fixed my problem. one question:

java2wsdl takes WSDL url as a param. Should *that* url include ?wsdl since it ends up being included in the resulting WSDL as:

<wsdlsoap:address location="http://localhost:8081/SimDatacenter/services/SimDatacenter?wsdl"/> (as i understand location=.. must refer to where wsdl can be actually retrieved. if '?wsdl' is omitted, the url won't return the doc).

If so, wsdl.url params to java2wsdl and wsdl2java ant tasks will be different. Just want to ensure that's the standard way...

-nikita


Rajesh Nair wrote:

Hi Nikita,
    Change the port name in the wsdl from "SimDatacenter?wsdl" to "
SimDatacenter". Also change the address location from
"http://localhost:8081/SimDatacenter/services/SimDatacenter?wsdl"; to
"http://localhost:8081/SimDatacenter/services/SimDatacenter";

HTH
-Rajesh


-----Original Message-----
From: Nikita Tovstoles [mailto:[EMAIL PROTECTED] Sent: Thursday, July 28, 2005 4:39 PM
To: [email protected]
Subject: wsdl2java: why is "?wsdl" getting appended "service name" in
generated *.wsdd?

Hi,

I'm using java2wsdl, wsdl2java to expose a webservice. For some reason, wsdl2java alters the name of the service by appending ?wsdl to the name (see attached generated wsdl and wsdd files). Why is that?

Also, if I run deploy.wsdd, AdminServlet lists "SimDatacenter?wsdl" (sic) as one of the services published, but when I click on "wsdl" link (i.e. .../SimDatacenter?wsdl?wsdl), I get "No service available at this URL". However, I am able to view WSDL of service "Version". Axis is part

of my web-app and Log4j is turned up to ALL, yet no axis-related error messages in app server's log files appear, except for (apparently no-big-deal server-config.wsdd not found" at start-up).

Is the second problem related to the renaming problem, or is it something else? How can I go about tracking this down?

thanks
-nikita


Here are my ant tasks:

   <!-- generate web service xml and stubs -->
   <target name="generate-ws" depends="compile">
       <!-- produce WSDL from our java sources -->
       <axis-java2wsdl output="${ws.localfile}"
location="${ws.url}" namespace="urn:SimDatacenter"
       classname="demolab.simdatacenter.service.SimDatacenter"
classpath="build"> <mapping namespace="urn:SimDatacenter" package="demolab.simdatacenter.service"/> <mapping namespace="urn:SimDatacenter/types" package="demolab.simdatacenter.common"/> </axis-java2wsdl> <!-- produce service-side stubs with wsdl2java --> <axis-wsdl2java serverside="true"
           skeletondeploy="true"
           deployscope="Session"
           output="scratch"
           verbose="true"
implementationclassname="demolab.simdatacenter.service.SimDatacenterImpl
"
url="xml/SimDatacenterService.wsdl"> <mapping namespace="urn:SimDatacenter" package="demolab.simdatacenter.service"/> <mapping namespace="urn:SimDatacenter/types" package="demolab.simdatacenter.common"/>
       </axis-wsdl2java>
<!-- copy ws-generated sources into scratch -->
       <copy todir="${ws.generated.dir}">
<fileset dir="scratch" includes="**/*SoapBinding*.java **/SimDatacenterServic*.java"/>


       </copy>
       <copy todir="xml" flatten="true">
<fileset dir="scratch" includes="**/*.wsdd"/>


</copy> </target>



--
===================================
Nikita Tovstoles

Demolab, Office of Strategic Insight
Sun Microsystems, Inc.
4170 Network Circle
USCA17, Office 3705
Mailstop USCA17-205
Santa Clara CA 95054
e-mail: [EMAIL PROTECTED]
office: 408-276-5348 / x15348
cell: 650-996-8173
===================================

Reply via email to