ok was using beta 2! thanks! supriyo
--- [EMAIL PROTECTED] wrote: > Which version of AXIS are you running? The nightly > builds have that > sample. And I believe beta 3 does as well. I'm > pretty sure beta 2 does > not. > > dynamic proxy requires the SEI. DII does not. > > Russell Butek > [EMAIL PROTECTED] > > > Supriyo Chatterjea <[EMAIL PROTECTED]> > on 07/18/2002 09:32:26 > AM > > Please respond to [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: > Subject: Re: Using WSDL with Axis > > > > Nope don't seem to have any file called > samples/jaxrpc/hello/HelloClient.java. Did you > mistype > the name by any chance? > > As for my second question - this is what I'm trying > to > do: > > I've got 2 devices, Device A and Device B. > > Device A is providing a service and B would like to > use the service provided by A. > > Device B has the following information about Device > A: > - URL of the WSDL file of Device A, e.g. > (http://deviceA/dev-a.wsdl) > - name of the method name it wishes to call and the > arguments that are required > - it does _not_ have the SEI > > Would it be possible for Device B to now invoke the > service provided by Device A? So can Device B go the > the WSDL file of Device A, pick out the binding > information for the required method and then invoke > the service? > > So the SEI is required on both the client and the > server. Does that mean that the client needs to have > the SEI for every single service it might want to > invoke? > > Would you call the scenario I've described above > dynamic proxy creation or DII? Then I'd know which > path to take and which example to follow. > > Thanks, > Supriyo > > > --- [EMAIL PROTECTED] wrote: > 1 - > WidgetPriceSoapBindingImpl.java - server-side > > implementation template > > (server-side only) > > 2 - WidgetPrice.java - the interface for the > service > > (often called the SEI > > - Service Endpoint Interface) (both client and > > server side) > > 3 - WidgetPriceService.java - the interface used > to > > get the client-side > > proxy/stub implementation of the SEI (generated > from > > the WSDL service) > > (client-side only) > > 4 - WidgetPriceServiceLocator.java - > implementation > > of WidgetPriceService > > (client-side only) > > 5 - WidgetPriceSoapBindingSkeleton.java - > > server-side, delegates call to > > actual implementation (server-side only) > > 6 - WidgetPriceSoapBindingStub.java - client-side > > proxy implementation > > (client-side only) > > 7 - deploy.wsdd - server-side deployment info > > (server-side only) > > 8 - undeply.wsdd - server-side used to undeploy a > > service (server-side > > only) > > > > In the simplest world, you can just call > > > > WidgetPrice wp = new > > WidgetPriceSoapBindingStub(...); > > > > But that code's not very portable. The proper > thing > > - the JAX-RPC thing - > > to do - as the samples show, is to start with the > > ServiceFactory, use it to > > get a Service, and use the service to get the stub > > implementation. > > > > I'm not sure what you mean by your #2. Do you > want > > to create a proxy > > dynamically? Yes, you can do that. You need the > > WSDL and the SEI. See > > samples/jaxrpc/hello/HelloClient.java. If you > want > > to do DII (dynamic > > invocation interface) then you don't even need the > > SEI or WSDL, but then > > you have to do EVERYTHING yourself: add > parameters, > > add properties (like > > endpoing URL), invoke the operation. See > > samples/jaxrpc/GetInfo.java > > > > Russell Butek > > [EMAIL PROTECTED] > > > > > > Supriyo Chatterjea > <[EMAIL PROTECTED]> > > on 07/18/2002 07:45:51 > > AM > > > > Please respond to [EMAIL PROTECTED] > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: Using WSDL with Axis > > > > > > > > Hi, > > > > I've got a couple of questions about using WSDL > with > > Axis. > > > > 1. I notice that in example 6 of the userguide, > > after > > using the WSDL2Java tool, the following files are > > generated: > > > > 1 - WidgetPriceSoapBindingImpl.java > > 2 - WidgetPrice.java > > 3 - WidgetPriceService.java > > 4 - WidgetPriceServiceLocator.java > > 5 - WidgetPriceSoapBindingSkeleton.java > > 6 - WidgetPriceSoapBindingStub.java > > 7 - deploy.wsdd > > 8 - undeply.wsdd > > > > I understand that some of these are meant to be on > > the > > client and some of them are supposed to be on the > > server. > > > > - My question is, why is it that you need to have > > certain Java files on the client side? > > > > - Don't you just need a single file on the client > > that > > invokes the service? > > > > - Which files listed above need to be on the > server > > and which ones need to be on the client? > > > > - What exactly is each file for? > > > > 2. Also, suppose a client wishes to access a > service > > on a server (both running on Axis), would it be > > possible for the client to access the service if > it > > *only* knows the URL of the WSDL file on the > server > > providing the service? > > > > Thanks, > > Supriyo > > > > __________________________________________________ > > Do You Yahoo!? > > Win a DV camera, join our "30 Seconds of Fame" > > contest > > http://sg.movies.yahoo.com > > > > __________________________________________________ > === message truncated === __________________________________________________ Do You Yahoo!? Win a DV camera, join our "30 Seconds of Fame" contest http://sg.movies.yahoo.com
