Re: Re: Axis2 is ignoring my WSDL
*PLEASE* create a jira issue, stating the behaviour you wish. -- dims 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: axis-user@ws.apache.org 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: 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] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Axis2 is ignoring my WSDL
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: axis-user@ws.apache.org 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: 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]
RE: Re: Axis2 is ignoring my WSDL
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: axis-user@ws.apache.org 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: 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]
Re: Axis2 is ignoring my WSDL
On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: But..If the wsdl you provide (either its content or style) is hosed there is no way for the program to correct it However.. If the program is *somehow* able to intuit from the services operations/methods and parameter(s) what the generated operation and the resulting request and response parameters should be *then* that feature should definitely be supported If I understand you correctly, you're saying that if you have a "bad" .wsdl (whatever that might mean) in your .aar, then Axis should ignore it and generate its own if it can before it pukes. I can't see that being a good thing in my situation. If I have a .wsdl in my .aar that I put there at build time, it means that anyone who has a copy of my .aar has my wsdl and they are going to be coding against it--at least they'd better if they hope to talk to my service and get meaningful results! Now, if you implement this automagical fall-back (which is what you're proposing), then the contract that I have built into my deployed package--the one I'm telling people they *need* to code against--is not going to match what happens in production. So, when a developer codes against a "broken" built WSDL, he's going to be in for a very rude awakening when he finally deploys his client(s)--the contract that I advertised does not reflect reality. At best, it'll just plain bork...but at worst, it may introduce a very subtle, hard-to-track bug. In my experience, it's better to fail in an obvious manner if you cannot guarantee completely safe fallback. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
Good Evening All- I'm finding org.apache.axis2.engine.Service class doesnt exist in my distro's is this a new class? I do however see org.apache.axis2.Service class from core.jar- thanks, M- * 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: "Martin Gainty" <[EMAIL PROTECTED]> To: "D.Kreft" <[EMAIL PROTECTED]>; Sent: Thursday, September 21, 2006 6:21 PM Subject: Re: Axis2 is ignoring my WSDL > You have to start from somewhere ..in our case a definition that is both > complete and syntactically correct > But..If the wsdl you provide (either its content or style) is hosed there is > no way for the program to correct it > However.. > If the program is *somehow* able to intuit from the services > operations/methods and parameter(s) what > the generated operation and the resulting request and response parameters > should be > *then* that feature should definitely be supported > +1 > M- > * > 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: "D.Kreft" <[EMAIL PROTECTED]> > To: ; "Martin Gainty" <[EMAIL PROTECTED]> > Sent: Thursday, September 21, 2006 5:52 PM > Subject: Re: Axis2 is ignoring my WSDL > > >> On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: >> >>> What I found is.. if you use any style other than RPC the wsdl's wont be >>> created under AXIS2 >> >> ...which I maintain is an unnecessary "feature". One should be able to >> specify his own WSDL regardless of what the messageReceiver is set to >> be for that service *and* be able to drop it in the appropriate place. >> Altering the behavior of the WSDL generation based upon the seemingly >> decision that RPC* methods cannot use a pre-generated WSDL does >> nothing more than apply arbitrary rules of engagement and remove power >> from the developer. >> >> No software developer can possibly anticipate all the "crazy" ways >> that other developers will want to use his products or services, so >> it's not a good idea for him to pretend like he knows exactly how >> everyone is going to use them. Software should have sensible, >> intuitive default behavior and allow for developers to deviate from >> the "norm" (whatever that is) by flipping a few bits. One should not >> have to "flip bits" to achieve sensible behavior. >> >> -dan >>
Re: Axis2 is ignoring my WSDL
You have to start from somewhere ..in our case a definition that is both complete and syntactically correct But..If the wsdl you provide (either its content or style) is hosed there is no way for the program to correct it However.. If the program is *somehow* able to intuit from the services operations/methods and parameter(s) what the generated operation and the resulting request and response parameters should be *then* that feature should definitely be supported +1 M- * 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: "D.Kreft" <[EMAIL PROTECTED]> To: ; "Martin Gainty" <[EMAIL PROTECTED]> Sent: Thursday, September 21, 2006 5:52 PM Subject: Re: Axis2 is ignoring my WSDL > On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: > >> What I found is.. if you use any style other than RPC the wsdl's wont be >> created under AXIS2 > > ...which I maintain is an unnecessary "feature". One should be able to > specify his own WSDL regardless of what the messageReceiver is set to > be for that service *and* be able to drop it in the appropriate place. > Altering the behavior of the WSDL generation based upon the seemingly > decision that RPC* methods cannot use a pre-generated WSDL does > nothing more than apply arbitrary rules of engagement and remove power > from the developer. > > No software developer can possibly anticipate all the "crazy" ways > that other developers will want to use his products or services, so > it's not a good idea for him to pretend like he knows exactly how > everyone is going to use them. Software should have sensible, > intuitive default behavior and allow for developers to deviate from > the "norm" (whatever that is) by flipping a few bits. One should not > have to "flip bits" to achieve sensible behavior. > > -dan >
Re: Axis2 is ignoring my WSDL
On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: What I found is.. if you use any style other than RPC the wsdl's wont be created under AXIS2 ...which I maintain is an unnecessary "feature". One should be able to specify his own WSDL regardless of what the messageReceiver is set to be for that service *and* be able to drop it in the appropriate place. Altering the behavior of the WSDL generation based upon the seemingly decision that RPC* methods cannot use a pre-generated WSDL does nothing more than apply arbitrary rules of engagement and remove power from the developer. No software developer can possibly anticipate all the "crazy" ways that other developers will want to use his products or services, so it's not a good idea for him to pretend like he knows exactly how everyone is going to use them. Software should have sensible, intuitive default behavior and allow for developers to deviate from the "norm" (whatever that is) by flipping a few bits. One should not have to "flip bits" to achieve sensible behavior. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 is ignoring my WSDL
Makes sense to me also. It should not be ignored by default. -vc -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 5:12 PM To: axis-user@ws.apache.org Subject: Re: Axis2 is ignoring my WSDL D.Kreft wrote: > Wait a second... > > It seems *really* counter-intutive to have to supply a configuration > setting to use a file that one intentionally puts in his .aar so that > Axis can use it. It was my understanding after reading the > documentation that a WSDL file in the META-INF directory was supposed > to inhibit the dynamic generation of a WSDL. Would it not be more > reasonable to use this as the default behavior and then provide an > option to *ignore* the supplied WSDL for those special cases when one > would want to do that? This makes sense to me. Anyone have an argument for why a supplied WSDL should be ignored by default? - Dennis - 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]
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: 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] > >
Re: Axis2 is ignoring my WSDL
D.Kreft wrote: Wait a second... It seems *really* counter-intutive to have to supply a configuration setting to use a file that one intentionally puts in his .aar so that Axis can use it. It was my understanding after reading the documentation that a WSDL file in the META-INF directory was supposed to inhibit the dynamic generation of a WSDL. Would it not be more reasonable to use this as the default behavior and then provide an option to *ignore* the supplied WSDL for those special cases when one would want to do that? This makes sense to me. Anyone have an argument for why a supplied WSDL should be ignored by default? - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 is ignoring my WSDL
Hi, I support Dan's views. We are creating Java Interfaces first and then WSDLs from those interfaces, so that an external non-java client can know about the contract. The implementation of those interfaces will happen in future. If we choose RPCMessageReceivers and deploy services, then Axis2 will start creating its own WSDLs. At this point probably the WSDL which I gave to external system may specify something else then what being generating by AXIS2. An example would be message and part names in WSDL itself, which may be different between my WSDL and AXIS2 generated WSDL. So I guess, definitely, I need an option where I can force Axis to use my WSDL. I hope true will work for RPCMessgereceiver also. -vc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft Sent: Thursday, September 21, 2006 4:05 PM To: axis-user@ws.apache.org Subject: Re: Axis2 is ignoring my WSDL 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]
Re: Axis2 is ignoring my WSDL
The nightly build has a Java2WSDL.sh, which will get me there, I'm sure...but is there documentation on how to use it (i.e. the arguments it takes)? There's no javadoc in the nightly docs snapshot for org.apache.ws.java2wsdl.Java2WSDL. Or am I relegated to source diving? -dan On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > > > 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 ? > > I'm not familiar with either xmlbeans or ADB, but after a cursory > examination it would appear that they do not offer > Java-to- functionality--they seem to work the other > way around. I'm a lot better at writing Java than I am at writing > metadata object descriptors...so I'd like to save myself to tedium of > having to write my own service descriptions at build time. > > -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]
Re: Axis2 is ignoring my WSDL
java2wsdl is what you are after I believe . Its a bat / sh file under the bin dir. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > 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 ? I'm not familiar with either xmlbeans or ADB, but after a cursory examination it would appear that they do not offer Java-to- functionality--they seem to work the other way around. I'm a lot better at writing Java than I am at writing metadata object descriptors...so I'd like to save myself to tedium of having to write my own service descriptions at build time. -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]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: 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 ? I'm not familiar with either xmlbeans or ADB, but after a cursory examination it would appear that they do not offer Java-to- functionality--they seem to work the other way around. I'm a lot better at writing Java than I am at writing metadata object descriptors...so I'd like to save myself to tedium of having to write my own service descriptions at build time. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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]
Re: Axis2 is ignoring my WSDL
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]
Re: Axis2 is ignoring my WSDL
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 The jist of it is that via databinding with xmlbeans, adb, jibx etc you will have your own wsdl. With RPC you are not using your own wsdl and axis2 will generate one for you. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > With a nightly or recent build try: > > true Okay, I tried this and I get no love from Axis2. I've got the WSDL in place: $ jar -tf services/pbqs.aar | grep wsdl META-INF/pbqs.wsdl And the parameter set: true But I'm being told: Unable to generate WSDL for this service Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. There is absolutely nothing printed to my catalina.out to indicate what the problem might be. FWIW, all of my messageReceivers are set to be org.apache.axis2.rpc.receivers.RPCMessageReceiver. Any guesses as to what's going on? In case it helps... $ md5sum axis2.war 32f4327ec0dbc733a007327deca40d64 axis2.war -dan > > Or wait for the upcomming release in about a week or so. > > HTH, > Robert > > On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > > I'm a bit stumped here. I've been scouring documentation, articles, > > commentaries and the like for two days, so now I'm going to pester you > > fine folks. :-) > > > > I am generating a wsdl at build time and inserting into the WEB-INF > > directory in my .aar file like so: > > > > $ jar -tf services/pbqs.aar | grep wsdl > > META-INF/PBQS.wsdl > > > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > > couldn't find one.) > > > > But when I issue the "?wsdl" command against my service (running under > > Tomcat, in case it matters), the WSDL I get back is most definitely > > *not* the one I had generated. Any ideas on why this might be? This > > worked fine under Axis1.x, but I cannot for the life of me get it to > > work under Axis2. > > > > In case you're inclined to respond with "Just use the > > automagically-generated WSDL", well, I'd rather not at this point. For > > reasons I'd rather not go into, having a WSDL that describes the > > service *as it was built* would be beneficial to me (and the > > developers at my company who may need to deploy an older version of > > the service for some reason). > > > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > > generating a WSDL is far less tedious. > > > > -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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: true Okay, I tried this and I get no love from Axis2. I've got the WSDL in place: $ jar -tf services/pbqs.aar | grep wsdl META-INF/pbqs.wsdl And the parameter set: true But I'm being told: Unable to generate WSDL for this service Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. There is absolutely nothing printed to my catalina.out to indicate what the problem might be. FWIW, all of my messageReceivers are set to be org.apache.axis2.rpc.receivers.RPCMessageReceiver. Any guesses as to what's going on? In case it helps... $ md5sum axis2.war 32f4327ec0dbc733a007327deca40d64 axis2.war -dan Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > I'm a bit stumped here. I've been scouring documentation, articles, > commentaries and the like for two days, so now I'm going to pester you > fine folks. :-) > > I am generating a wsdl at build time and inserting into the WEB-INF > directory in my .aar file like so: > > $ jar -tf services/pbqs.aar | grep wsdl > META-INF/PBQS.wsdl > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > couldn't find one.) > > But when I issue the "?wsdl" command against my service (running under > Tomcat, in case it matters), the WSDL I get back is most definitely > *not* the one I had generated. Any ideas on why this might be? This > worked fine under Axis1.x, but I cannot for the life of me get it to > work under Axis2. > > In case you're inclined to respond with "Just use the > automagically-generated WSDL", well, I'd rather not at this point. For > reasons I'd rather not go into, having a WSDL that describes the > service *as it was built* would be beneficial to me (and the > developers at my company who may need to deploy an older version of > the service for some reason). > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > generating a WSDL is far less tedious. > > -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]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: Is the omission of log4j in the nightly build intentional? $ jar -tf axis2.war.release | grep log4 WEB-INF/lib/log4j-1.2.13.jar WEB-INF/lib/log4j-LICENSE.txt WEB-INF/classes/log4j.properties $ jar -tf axis2.war.nightly | grep log4 WEB-INF/lib/log4j-LICENSE.txt WEB-INF/classes/log4j.properties -dan true Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > I'm a bit stumped here. I've been scouring documentation, articles, > commentaries and the like for two days, so now I'm going to pester you > fine folks. :-) > > I am generating a wsdl at build time and inserting into the WEB-INF > directory in my .aar file like so: > > $ jar -tf services/pbqs.aar | grep wsdl > META-INF/PBQS.wsdl > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > couldn't find one.) > > But when I issue the "?wsdl" command against my service (running under > Tomcat, in case it matters), the WSDL I get back is most definitely > *not* the one I had generated. Any ideas on why this might be? This > worked fine under Axis1.x, but I cannot for the life of me get it to > work under Axis2. > > In case you're inclined to respond with "Just use the > automagically-generated WSDL", well, I'd rather not at this point. For > reasons I'd rather not go into, having a WSDL that describes the > service *as it was built* would be beneficial to me (and the > developers at my company who may need to deploy an older version of > the service for some reason). > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > generating a WSDL is far less tedious. > > -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]
Re: Axis2 is ignoring my WSDL
Wait a second... It seems *really* counter-intutive to have to supply a configuration setting to use a file that one intentionally puts in his .aar so that Axis can use it. It was my understanding after reading the documentation that a WSDL file in the META-INF directory was supposed to inhibit the dynamic generation of a WSDL. Would it not be more reasonable to use this as the default behavior and then provide an option to *ignore* the supplied WSDL for those special cases when one would want to do that? -dan On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: services.xml Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > > > With a nightly or recent build try: > > > > true > > Is this to go into the axis2.xml or the services.xml? I'm guessing the > latter, but hoping to save myself some time (and more beating my head > against the wall). > > Thanks. > > -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]
Re: Axis2 is ignoring my WSDL
services.xml Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > With a nightly or recent build try: > > true Is this to go into the axis2.xml or the services.xml? I'm guessing the latter, but hoping to save myself some time (and more beating my head against the wall). Thanks. -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]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: true Is this to go into the axis2.xml or the services.xml? I'm guessing the latter, but hoping to save myself some time (and more beating my head against the wall). Thanks. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
With a nightly or recent build try: true Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: I'm a bit stumped here. I've been scouring documentation, articles, commentaries and the like for two days, so now I'm going to pester you fine folks. :-) I am generating a wsdl at build time and inserting into the WEB-INF directory in my .aar file like so: $ jar -tf services/pbqs.aar | grep wsdl META-INF/PBQS.wsdl (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I couldn't find one.) But when I issue the "?wsdl" command against my service (running under Tomcat, in case it matters), the WSDL I get back is most definitely *not* the one I had generated. Any ideas on why this might be? This worked fine under Axis1.x, but I cannot for the life of me get it to work under Axis2. In case you're inclined to respond with "Just use the automagically-generated WSDL", well, I'd rather not at this point. For reasons I'd rather not go into, having a WSDL that describes the service *as it was built* would be beneficial to me (and the developers at my company who may need to deploy an older version of the service for some reason). I'd also much prefer to *not* go from WSDL->Java--starting with Java and generating a WSDL is far less tedious. -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]