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.
aspectjrt.jar
axis-1.2.1.jar
commons-discovery-0.2.jar
commons-logging-1.0.4.jar
jaxrpc.jar
saaj.jar
wsdl4j-1.5.1.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