Thank u for the response. I am not familiar with the underlying implementation of AXIS. Even JAX-RPC is its fundation, all that should really be transparent to the web services developers. Looking at the samples, some of them doesn't the stub and skeleton stuff, just and client and a service, handlers(if any), like the message smaple, attachment sample and the ones under usersguide. Could you explain when the JAX-RPC is needed? also are you going to have interoperability issues (with .NET) when JAX-RPC is exposed?
Thanks, --- Steve Loughran <[EMAIL PROTECTED]> wrote: > > ----- Original Message ----- > From: "alanz" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, October 27, 2002 09:02 > Subject: What is wsdl2java for? > > > > It seems to me WSDL2Java should generate the > > testclient and the service classes for the web > service > > described in the WSDL. > > it does just that if you ask it nicely, -testcase > and -server, I think > > > But instead, wsdl2java > > generates a bunch of RMI like stubs and skeletons > and > > interfaces. > > does that too > > >I guess this effort is for the JAX-RPC > > support? > > no, the stubs are what clients need to call the > service > > > For people doing Web Services this seems > > irrelevant? > > no, wsdl2java is nearly essential to a build > process. > > >Maybe because of my lack of knowledge on > > JAX-RPC? > > > more your lack of knowledge on how to use wsdl2java > - look at all its otions > and play with it. > > >What exactly is the JAX-RPC support have anything > to do with SOAP web > services? > > JAX-RPC is the underlying standard API for SOAP in > Java, > > > > __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
