Thanks for the link, a good read. I realized that my real problem was that I
was generating server side code when I really wanted a client. Using the
skeleton was only confusing because I shouldn't have been using it. I
generated without the -ss flag and it generated the stub which is exactly what
I was looking for.
Which leads to my other post about the stub getting compiler errors...
Thanks again,
Jesse
----- Original Message ----
From: robert lazarski <[EMAIL PROTECTED]>
To: [email protected]; Jesse Vitrone <[EMAIL PROTECTED]>
Sent: Wednesday, September 13, 2006 8:36:42 PM
Subject: Re: [Axis2] service client skeleton
Have you looked at the migration guide? If its lacking, could you give
us some feedback to imnprove it?
http://ws.apache.org/axis2/1_0/migration.html#data_binding
Robert
On 9/13/06, Jesse Vitrone <[EMAIL PROTECTED]> wrote:
> I'm currently using Axis 1.4 to generate a client from a WSDL, and I'd like
> to switch to Axis2. I'm a little confused by the different classes it
> generates for the client though.
>
> With my "BookingService" wsdl, I currently use the generated
> BookingServiceLocator to set the endpoint on the fly, and get the facade,
> then use the facade to send the request.
>
> I don't see a locator anywhere in the code generated by Axis2, but I do see a
> BookingServiceSkeleton, but I can't find any good examples on how to use the
> generated skeleton. I need to be able to set the endpoint, and call the
> "createBooking" method that's on the skeleton, but I don't see how to set the
> endpoint.
>
> There's this example from the docs that seems close to what I want:
>
> try {
> OMElement payload = ClientUtil.getEchoOMElement();
>
> Options options = new Options();
> options.setTo(targetEPR); // this sets the location of MyService
> service
>
> ServiceClient serviceClient = new ServiceClient();
> serviceClient.setOptions(options);
>
> OMElement result = sender.sendReceive(payload);
>
> System.out.println(result);
>
> } catch (AxisFault axisFault) {
> axisFault.printStackTrace();
> }
> }But it leaves out the details like what is "ClientUtil", and what is
> "sender" that's calling sendRecieve?
>
> Does anyone have a good simple example of how to set the endpoint and what to
> do with the Skeleton?
>
> Thanks in advance.
>
>
>
>
>
> ---------------------------------------------------------------------
> 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]
