i can really work but then I would need your ample guidance as I am a newbie to the volunteer world and am not even a guru for all this but if you can guide me I can really work and put time to do the stuff you guys can explain me.
Bhanu Pabreja -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Saturday, May 31, 2003 12:18 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Best practices question Many of the commercial Java implementations (WASP, GLUE, Cape Clear, XMLBus) autogenerate the schema, WSDL, and UDDI documents for you also. There's no reason why we can't do the same in Axis. Any volunteers? Anne ----- Original Message ----- From: "Mark Galbreath" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, May 31, 2003 10:43 AM Subject: RE: Best practices question > What really needs to happen is the availability of tools that auto-generate > the XML schema, WSDL, and UDDI documents so developers don't have to waste > time learning and implementing a technology that does not return benefit > relative to amount of effort. These documents are tedious to produce at > best and a serious waste of development time at worse. I believe .NET 2003 > already does this. > > Mark > > -----Original Message----- > From: Ted Neward [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 31, 2003 10:39 AM > > The thing that many developers (IMHO) will find more complicated about > doc/literal as opposed to an rpc/encoded scenario as its done today is that > types must (for all intents and purposes) be specified in schema, rather > than in Java (or C#, or whatever your "source" language is). That requires > you to learn and understand the nuances of XML Schema, which are somewhat > nontrivial. > > That said, though, I think ultimately it's the best approach to take, in > order to maximize the interoperability of your web service, which (if you > think about it) is really the whole point in the first place. > >
