Hi Guys, Even though this discussion took off in the user list it seems more relevant to the dev list (so I'm forwarding it to the dev list). BTW it would be good if one of you can open a Jira so that this won't be just forgotton :)
Ajith On 9/22/06, Bhatra, Junaid <[EMAIL PROTECTED]> wrote:
Going further on this, even if you do NOT use RPCMessageReceiver and supply your own WSDL, Axis2 **still** modifies/overrides your WSDL unless you specify the "useOriginalwsdl" parameter. The logic seems inverted to me. In contrast, the default behavior of Axis 1.x is to honor the user-specified WSDL. -----Original Message----- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 5:19 PM To: [email protected] Subject: Re: Axis2 is ignoring my WSDL What I found is.. if you use any style other than RPC the wsdl's wont be created under AXIS2 Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "robert lazarski" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, September 21, 2006 4:10 PM Subject: Re: Axis2 is ignoring my WSDL > You can use your own wsdl provided you use any other message receiver > except for RPC*. If you have a wsdl that you made yourself or got > from somewhere, why not just use databinding via xmlbeans or adb ? > > Robert > > On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: >> On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: >> >> > If you are using RPCMessageReceiver it doesn't make sense to use your >> > own WSDL . This is a FAQ: >> > >> > http://www.wso2.net/kb/104 >> >> Yeah, I saw that a couple of days ago. I think I actually read it more >> than once. >> >> The explanation of why I would *really* like to have a WSDL generated >> at build time is not something I really wanted to get into, so I'll >> try to keep this short and sweet. >> >> The presence of a WSDL at build time makes it much easier for builds >> of other packages (the smallest unit of software development at my >> company) to depend upon my service (at build time)--and it also makes >> it possible to determine if a particular build of my service has the >> contract that another developer is interested in. It is unacceptable >> in our environment to have to query a WSDL from a running service at >> build time--developers might not have network access, they might be >> trying to code to a built-but-not-yet-deployed WSDL, or any one of a >> number of different reasons. >> >> But philosophical arguments aside, I still don't understand why my >> wsdl would not be used if it is where the Axis2 docs say it should be. >> >> -dan >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
