I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the
message receiver class. Axis2 is auto generating the wsdl. Can I know where
I can find the physical location of the file on my file system??
The WSDL is generated on-demand... it isn't stored. If you want to
store it you can use a browser (Save As...) or wget to grab it.
Paul
On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote:
I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the
message
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 11:57 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL location
The WSDL is generated on-demand... it isn't stored. If you want to
store it you can use a browser (Save As...) or wget to grab it.
Paul
]
Sent: Thursday, January 10, 2008 11:57 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL location
The WSDL is generated on-demand... it isn't stored. If you want to
store it you can use a browser (Save As...) or wget to grab it.
Paul
On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL
-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 12:19 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL location
Anjana
I'm not clear changing the WSDL file is the right solution here, but
you can do it. You save the WSDL, add it into the service archive, and
then set
on
altering the public wsdl location. So, I moved my wsdls into a
publicly accessible (outside of WEB-INF) directory. Now I can
easily generate client stubs. However, I cannot submit a soap
request to these locations.
Is there a way to configure
I've read up on how to tell Axis to use a specific wsdl instead of auto-generating them. I still have not found any information on altering the public wsdl location. So, I moved my wsdls into a publicly accessible (outside of WEB-INF) directory. Now I can easily generate client stubs. However, I