Hey Dan, Sorry for the confusion. I meant that you can run wsdl2java right now against the wsdl in the "simple" sample (or any other wsdl in the samples), and see that the generated java operation methods don't have parameters. I have a demo wsdl that I'm currently working on, but it is based off the sample, so it's not much different. This is probably not a big issue, but if it is a bug, hopefully it can be fixed at some point. -Vinh
-----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 1:41 PM To: [email protected] Subject: RE: message types not checked? This is not a problem with wsdl2java, but with time - the samples were made long before wsdl2java was written, and we never changed them because, well, they worked. You don't have to run wsdl2java on any of the samples - you just run 'ant' and it makes the deployable app. While Muse can support a few different conventions of WSDL design, wsdl2java has to be a bit more strict in order to be consistent. Thus, the conventions here: http://ws.apache.org/muse/docs/2.0.0/manual/tools/wsdl-conventions.html Perhaps we should open a JIRA item to make sure all sample project WSDLs follow every wsdl2java convention for those that try to re-create them. But for now, if you follow the wsdl2java conventions on your own WSDLs, the tool should work. :) Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 10/27/2006 04:35:11 PM: > Hi Andrew, > You can take a look at the "simple" example that came with the > Muse-2.0.0 download. The wsdl specifies that the "FirstOperation" > should receive a String parameter, and return a String parameter. > These are defined in the schema types section. When you run > wsdl2java, it creates a corresponding class that has no parameters in > the operation methods. The same happens for the "SecondOperation". > > Then, notice that in the sample's "src" directory that includes the > modified version of these classes, the owner had to modify the > operation methods and add the single String parameter. So in my > current project, after running wsdl2java, I also have to do this for > each generated operation method, and I must try to ensure that the > parameters match what is specified in the wsdl, if the operations are > defined to have any parameters. This is ok for a few operations, but > probably not if we have a lot of them. > > > > -----Original Message----- > From: Andrew Eberbach [mailto:[EMAIL PROTECTED] > Sent: Friday, October 27, 2006 12:59 PM > To: [email protected] > Subject: Re: message types not checked? > > 1) The wsdl2java script creates the java "stub" classes and an > operation method in each class, but the method is incomplete. No > parameters are generated in the method signature, even if the wsdl > indicates that a parameter is passed to the operation. Is this the > intended design, or is it up to the developer to fill in the correct > parameters in the java code? > > <ame>There should definitely be parameters in the methods. Can you > give an example of a wsdl that generates methods with no parameters > when the wsdl specifies parameters?</ame> > > --------------------------------------------------------------------- > 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]
