- Added support for v12 (removed support for v10).
- Both properties, version and alternateUrl from adwords.properties
are now used to construct the request URL. To make API call against
live account using v11, set "version=v11" and "alternateUrl=https://
adwords.google.com".
- Added support for new property "clientId" in adwords.properties.
It replaces previously used "clientEmail". In addition to supporting
clientEmail, "clientId" property introduces support for
clientCustomerId (e.g., "joe.sh...@gmail.com", "123-456-7890",
"1234567890").
- Bug fixes.
> - Added support for v12 (removed support for v10).
> - Both properties, version and alternateUrl from adwords.properties
> are now used to construct the request URL. To make API call against
> live account using v11, set "version=v11" and "alternateUrl=https://
> adwords.google.com".
> - Added support for new property "clientId" in adwords.properties.
> It replaces previously used "clientEmail". In addition to supporting
> clientEmail, "clientId" property introduces support for
> clientCustomerId (e.g., "joe.sh...@gmail.com", "123-456-7890",
> "1234567890").
> - Bug fixes.
> - Added support for v12 (removed support for v10).
> - Both properties, version and alternateUrl from adwords.properties
> are now used to construct the request URL. To make API call against
> live account using v11, set "version=v11" and "alternateUrl=https://
> adwords.google.com".
> - Added support for new property "clientId" in adwords.properties.
> It replaces previously used "clientEmail". In addition to supporting
> clientEmail, "clientId" property introduces support for
> clientCustomerId (e.g., "joe.sh...@gmail.com", "123-456-7890",
> "1234567890").
> - Bug fixes.
The previous jar that I have been using very successfully in my
production environment did not contain the javax.servlet classes.
They are now included in this jar which has a bad side effect of not
loading into tomcat:
Apr 8, 2008 1:23:04 PM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO: validateJarFile(/home/adlucent/damn/tomcat-production/webapps/
adlucent/WEB-INF/lib/adwords-api-1.0.0.jar) - jar not loaded. See
Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/
Servlet.class
I can re-jar it on my end, but wanted to post here as I would think
that using this jar within tomcat is not unique to my application.
Tim
On Apr 7, 10:25 am, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
I noticed there is a new release which includes a no dependency jar.
I also noticed the list of external dependencies in the README.
However I was wondering which of those jars are needed for compilation
and which are needed at run time. Again I can do this by trial and
error myself but it might be nice to have a clean list for those
trying to package up a tight tomcat install.
Tim
On Apr 8, 1:35 pm, tozor <t...@adlucent.com> wrote:
> The previous jar that I have been using very successfully in my
> production environment did not contain the javax.servlet classes.
> They are now included in this jar which has a bad side effect of not
> loading into tomcat:
> Apr 8, 2008 1:23:04 PM org.apache.catalina.loader.WebappClassLoader
> validateJarFile
> INFO: validateJarFile(/home/adlucent/damn/tomcat-production/webapps/
> adlucent/WEB-INF/lib/adwords-api-1.0.0.jar) - jar not loaded. See
> Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/
> Servlet.class
> I can re-jar it on my end, but wanted to post here as I would think
> that using this jar within tomcat is not unique to my application.
> Tim
> On Apr 7, 10:25 am, AdWords API Advisor <adwordsapiadvi...@google.com>
> wrote:
> > There will be a patch release this week which will include both JARs,
> > with and without dependencies.
> > --Stan
> > On Apr 4, 12:18 pm, Ian <ian_p_sy...@yahoo.co.uk> wrote:
I thought I would post a follow up to my investigation. The following
jars are needed at runtime along with the no dependency adwords-
api-1.0.1-loner.jar.
The j2ee.jar which is listed as an external dependency does not appear
to be needed, and in fact is the root cause of my original post (it
contains the java.servlet classes which tomcat objected to). In
addition this jar is HUGE (almost 7MB). Interestingly the previous
adwords jar file I was using for V11 (the one from the sourceforge
project) does not contain the j2ee.jar classes.
As a philisophical point, I think that the fewer dependencies the
better. Since this jar is a support jar for Adwords java application
writers, I'm not sure why it is necessary to have the commons-logging
(and in turn commons-discovery) dependencies. This seems unnecessary.
There used to be a term called "DLL hell" to refer to the morass of
disparate library dependencies required for Windows application
developers. The commons libraries tend to fall into the same trap
(e.g. you can't use commons-fileupload without commons-io). The
reason this is an issue is that all of these jars on the classpath can
result in much more memory intensive java applications.
Tim
On Apr 8, 1:54 pm, tozor <t...@adlucent.com> wrote:
> I noticed there is a new release which includes a no dependency jar.
> I also noticed the list of external dependencies in the README.
> However I was wondering which of those jars are needed for compilation
> and which are needed at run time. Again I can do this by trial and
> error myself but it might be nice to have a clean list for those
> trying to package up a tight tomcat install.
> Tim
> On Apr 8, 1:35 pm, tozor <t...@adlucent.com> wrote:
> > The previous jar that I have been using very successfully in my
> > production environment did not contain the javax.servlet classes.
> > They are now included in this jar which has a bad side effect of not
> > loading into tomcat:
I've gotten that error before when I had the adwords version set to
v12 but my code was compiled against v12. In my case I had an
incorrect setting in a properties file.
Tim
On Apr 8, 7:27 pm, pornllc <porn...@gmail.com> wrote:
> I've gotten that error before when I had the adwords version set to
> v12 but my code was compiled against v12. In my case I had an
> incorrect setting in a properties file.
> Tim
> On Apr 8, 7:27 pm, pornllc <porn...@gmail.com> wrote:
> > Is anyone else getting this error when trying to use the new -
> > loner.jar and the ReportService?
> > Code:
> > ReportInterface service = (ReportInterface)
> > user.getService(user.REPORT_SERVICE);
> Sorry I meant to say my version was set to v11 but my code was
> compiled against v12.
> Tim
> On Apr 8, 7:58 pm, tozor <t...@adlucent.com> wrote:
> > I've gotten that error before when I had the adwords version set to
> > v12 but my code was compiled against v12. In my case I had an
> > incorrect setting in a properties file.
> > Tim
> > On Apr 8, 7:27 pm, pornllc <porn...@gmail.com> wrote:
> > > Is anyone else getting this error when trying to use the new -
> > > loner.jar and the ReportService?
1) As a direct argument to an AdwordsUser constructor.
2) In the adwords.properties file. This file is used when the no arg
AdwordsUser constructor is used.
There is a sample adwords.properties in the directory where you
installed the adwords java package. Also the code in the
AdwordsUser.java (foound in src/com/google/api/adwords/lib) is pretty
easy to understand if you take a look at it.
Tim
On Apr 8, 9:43 pm, pornllc <porn...@gmail.com> wrote:
> I've only had experience before with working on v10 - is there
> something I need to do (method call, etc) to "set" the API to v12?
> On Apr 8, 5:59 pm, tozor <t...@adlucent.com> wrote:
> > Sorry I meant to say my version was set to v11 but my code was
> > compiled against v12.
> > Tim
> > On Apr 8, 7:58 pm, tozor <t...@adlucent.com> wrote:
> > > I've gotten that error before when I had the adwords version set to
> > > v12 but my code was compiled against v12. In my case I had an
> > > incorrect setting in a properties file.
|
