Looks like you just give it a file and it is opened as a file, relative to wherever the system thinks the current directory is.
I'll probably tap in some code to resolve against resources on the classpath if a file isnt found, as that would deem the better approach. ----- Original Message ----- From: "Daleiden, Mike" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 11:14 AM Subject: RE: Generated WSDL <> original WSDL Is the filename specified as an absolute path? Or is it relative to the web app? Please provide an example. -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: Re: Generated WSDL <> original WSDL ----- Original Message ----- From: "Tom Jordahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 7:13 AM Subject: RE: Generated WSDL <> original WSDL > Please keep in mind that Axis isn't "changing" the WSDL, it is > generating the WSDL from the Java classes it has at hand. The original WSDL is *gone*. Unless you keep it around with the <wsdlFile> property. What is the way to specify the filename? is it <property name="wsdlFile" value="foo"> or <wsdlfile>some file</wsdlfile> the way I've seen hinted The latter isnt in the schema (yet), and neither are in the (not yet existent) Axis configuration guide...
