Thanks, Jeff.

By the way, in comparing the Java interface generated by axis1
(apparently the default in Eclipse) and axis2, I noticed that some of
the structure of the data itself differs beyond how the security info
is handled: In these snippets, the commented-out version is axis2:

        Campaign cmp = addCampaign();
        //LanguageTarget lt = new LanguageTarget();
        //lt.setLanguages(new String[] {"English", "French"});
        //cmp.setLanguageTargeting(lt);
        cmp.setLanguageTargeting(new String[] {"English", "French"});

        Campaign cmp = addCampaign();
        GeoTarget geo = new GeoTarget();
        Circle c = new Circle();
        c.setLatitudeMicroDegrees(100);
        c.setLongitudeMicroDegrees(100);
        //ProximityTargets pt = new ProximityTargets();
        // pt.setCircles(new Circle[] { c });
        //geo.setProximityTargets(pt);
        geo.setProximityTargets(new Circle[] { c });
        cmp.setGeoTargeting(geo);

So I wonder if the axis1 client bindings would work with an axis2-
based server and vice-versa.

Bill



On Jul 14, 9:18 am, AdWords API Advisor <[email protected]>
wrote:
> Hello Bill,
>
>  You're just looking at some sample Java code, which is only one
> approach for accessing the AdWords API. We also have a Java client
> library available, which takes care of most of the details of using
> the SOAP service for you:
>
>  http://code.google.com/p/google-api-adwords-java/
>
>  I believe that the Java client library was also generated using Axis
> 1.x, and the ultimate reason for using that rather than Axis 2.x isn't
> something I'm familiar with. But it should work fine with the AdWords
> API SOAP service.
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Jul 13, 8:47 pm, waxriot <[email protected]> wrote:
>
> > It looks like adWords started as axis1 based on this example:
>
> >  http://code.google.com/p/adwords-api-java-samples/source/browse/trunk...
>
> > import org.apache.axis.client.Stub;
> >  ...
> >       // Define SOAP headers.
> >       ((Stub) service).setHeader(namespace, "email", email);
>
> > vs. "import org.axis2.client.Stub". Generating a client via axis2
> > seems to lead to an API wherein each call to a service needs to pass
> > all the verification info (e.g. CampaignServiceStub.java), in that the
> > Stub class lacks the setHeader() method. Is this bulky approach really
> > necessary, and if so why on earth, when axis1 was so lightweight?
>
> > Bill
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to