RE: Best practices question

[Bhanu Pabreja <pa...@infigroup.com>]

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:anne@manes.net]
Sent: Saturday, May 31, 2003 12:18 PM
To: axis-user@ws.apache.org; tneward@javageeks.com
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" <ma...@qat.com>
To: <ax...@ws.apache.org>; <tn...@javageeks.com>
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:tneward@javageeks.com]
> 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.
>
>

RE: Best practices question

[Davanum Srinivas <di...@yahoo.com>]

Here's where you can start....Visit http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages,
click on [Where can I get a list of current bugs?], pick one that you think you can fix, then when
you are ready with a fix, click on [How do I submit patches to Axis?] on how to submit a patch.
You can send emails to axis-dev@ mailing list for any issues/problems w.r.t development.

Thanks,
dims

--- Bhanu Pabreja <pa...@infigroup.com> wrote:
> 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:anne@manes.net]
> Sent: Saturday, May 31, 2003 12:18 PM
> To: axis-user@ws.apache.org; tneward@javageeks.com
> 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" <ma...@qat.com>
> To: <ax...@ws.apache.org>; <tn...@javageeks.com>
> 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:tneward@javageeks.com]
> > 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.
> >
> >
> 
> 
> 
> 


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com